-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fixing url parse errors #173
Comments
It appears that, for many invalid routes below the root, the 404 page isn't used; instead handlers frequently assume that the url is valid, and throw some sort of error when this isn't the case. I don't think it's feasible to handle 404 errors at the top-level router (as response handling is delegated), but perhaps for each subpage's routing it may be. |
Update: https://rollbar.com/compserv/hkn-rails/items/93/?person_page=0&#ip-addresses
File The root of this is bad url parsing: assuming a cast to Integer will work, and not handling any errors. |
Bug reproduction: navigate to any url of the form:
These are available on Rollbar as error 68, 93, 95, 99, 110.
These all stem from poor url parsing, especially assumed Integer conversion successes (errors are uncaught).
Ex: error 68.
Traceback: models/exam.rb.
Root cause: department (decoded from url) assumed to be found (no nil checks), causing dept.name to throw 'undefined method 'name''.
The text was updated successfully, but these errors were encountered: