You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when an error/exception occurs, Piwik returns a 200 HTTP status and that can mess up with a lot of things.
Current status:
Web
Tracker
Fatal error
200
200
PHP error
200
200
Exception
200
200
Target:
Web
Tracker
Fatal error
500
500
PHP error
500
500
Exception
?
?
For uncaught exceptions, we are not sure we want to return a 500 because exceptions could be for example "unknown idSite" which should be a 404. Same for 403 I guess (I haven't looked at the code)
However it definitely should not be a 200 as it is now. We should probably improve how exceptions are handled in some cases (404, 403…).
The text was updated successfully, but these errors were encountered:
Currently when an error/exception occurs, Piwik returns a 200 HTTP status and that can mess up with a lot of things.
Current status:
Target:
For uncaught exceptions, we are not sure we want to return a 500 because exceptions could be for example "unknown idSite" which should be a 404. Same for 403 I guess (I haven't looked at the code)
However it definitely should not be a 200 as it is now. We should probably improve how exceptions are handled in some cases (404, 403…).
The text was updated successfully, but these errors were encountered: