Returning HTTP 200 instead of HTTP 500 #293

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

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
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

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter 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

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

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Jul 19, 2015

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

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

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter 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
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