Skip to content

Update the default method when rendering a 404#2519

Open
jonodrew wants to merge 1 commit intomasterfrom
fix-token-error
Open

Update the default method when rendering a 404#2519
jonodrew wants to merge 1 commit intomasterfrom
fix-token-error

Conversation

@jonodrew
Copy link
Contributor

This was a very strange bug. We found that users visiting events/introduction-to-git-1/invitation/hello@codebar.io (we don't know how this url was generated) caused the application to crash. We fixed it with 6c83d92, but it bothered me that the 404 page was not our standard one.

It turns out that rails interprets a dot as a format separator. That meant the url was being parsed as events/introduction-to-git-1/invitation/hello@codebar., with a format of 'io'. In our previous application_controller.rb file, that was caught by the line format.all { head :not_found }.

The result of this should be a nice splash page whenever there's a 404, including where a URL is malformed.

This was a very strange bug. We found that users visiting `events/introduction-to-git-1/invitation/hello@codebar.io` (we don't know how this url was generated) caused the application to crash. We fixed it with 6c83d92, but it bothered me that the 404 page was not our standard one.

It turns out that rails interprets a dot as a format separator. That meant the url was being parsed as `events/introduction-to-git-1/invitation/hello@codebar.`, with a format of 'io'. In our previous application_controller.rb file, that was caught by the line `     format.all  { head :not_found }`.

The result of this should be a nice splash page whenever there's a 404, including where a URL is malformed.

Signed-off-by: jonathan.kerr <3410350+jonodrew@users.noreply.github.com>
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

Successfully merging this pull request may close these issues.

1 participant