Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publicServerURL (PSU) overriding mount in 2.2.5 #1395

Closed
3 tasks done
mutex007 opened this issue Apr 6, 2016 · 3 comments
Closed
3 tasks done

publicServerURL (PSU) overriding mount in 2.2.5 #1395

mutex007 opened this issue Apr 6, 2016 · 3 comments

Comments

@mutex007
Copy link

mutex007 commented Apr 6, 2016

Had an issue yesterday where the (PSU) was overriding the mount. The issue is the example of (PSU) in the readme.md file uses http://example.com. Of course this is misleading, since after you use a similar thing, all your files will be loaded back as http://example.com/files... instead of http://example.com/parse/files.. This will lead to a 404 not found request.

Could you possibly include this in the readme guide. That is change it to http://example.com/parse. or completely revert the (PSU) overriding the mount.

The update in particular is:

Adds ability to override mount with publicServerURL for production uses #1287 (flovilmart)

Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!

For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

Environment Setup

Steps to reproduce

Logs/Trace

@flovilmart
Copy link
Contributor

@mutex007 I believe this is a documentation problem, the publicServerURL is intended to be the same as serverURL but with a publicly accessible address. Can you confirm that with publicServerURL set as http://example.com/parse it's all working?

@mutex007
Copy link
Author

mutex007 commented Apr 6, 2016

Correct works with http://example.com/parse

Regards.

@flovilmart
Copy link
Contributor

I'll update the readme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants