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

Invalid URLs return HTTP 200 and does not indicate error #12

Open
leizleiz opened this issue Dec 20, 2016 · 3 comments
Open

Invalid URLs return HTTP 200 and does not indicate error #12

leizleiz opened this issue Dec 20, 2016 · 3 comments

Comments

@leizleiz
Copy link

  1. Download https://www.socallinuxexpo.org/scale/15x/foobar

Expected: Server returns HTTP 404 (Not found) and returns a templated page indicating error.
Actual: Server returns HTTP 200 (OK) and returns a templated page with no content in the middle.

@rgolan
Copy link
Collaborator

rgolan commented Dec 21, 2016

@irabinovitch
Copy link
Collaborator

irabinovitch commented Jan 24, 2017

@rgolan I could be misreading that ticket, but I think that refers to the /node/1/foo style urls rather than the aliases we generally use. Are we using pathauto to generate our url aliases, or something different?

@rgolan
Copy link
Collaborator

rgolan commented Jan 24, 2017

We are using pathauto. The reason Drupal doesn't return a 404 is because Drupal uses extra path elements as parameters. The page can either use them or ignore them. I don't understand why we care about this. They shouldn't be getting indexed by search engines.

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

No branches or pull requests

3 participants