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

Returning HTTP 200 instead of HTTP 500 #293

Closed
GoogleCodeExporter opened this issue Jul 19, 2015 · 3 comments
Closed

Returning HTTP 200 instead of HTTP 500 #293

GoogleCodeExporter opened this issue Jul 19, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Jul 19, 2015

See https://code.google.com/p/opencaching-api/issues/detail?id=20#c26.

In case of PHP fatal error, OCPL is returning error description along with the 
HTTP 200 status. Should be HTTP 500, with NO error description.

Original issue reported on code.google.com by rygielski on 18 Dec 2013 at 8:04

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Jul 19, 2015

I cannot replicate this issue on my OCPL-DEVEL VM. I have no idea why it 
doesn't work properly on OCPL production server.

Original comment by rygielski on 18 Dec 2013 at 8:15

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Jul 19, 2015

Original comment by rygielski on 3 Jan 2014 at 2:45

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Jul 19, 2015

Turns out, OCPL had "display_errors" set to "on" in production php.ini (!). It 
was set back to "off". OKAPI should return HTTP 500 error as expected.

Original comment by rygielski on 7 Jan 2014 at 11:41

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.