9

I've noticed that in SO sites some URLs don't give the standard error "Page not Found" with the waffles but a 404 error.

For example these URLs: https://meta.stackexchange.com/a/a/a/a/a/a/a/a/a/a/

https://meta.stackexchange.com/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/

are giving the standard error page, but if I add another slash (the 32nd), the Web Server gives another page, in some way "out of control":

https://meta.stackexchange.com/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/a/

I don't know if it's so important to notice but I wanted to try, because I work as programmer and sometimes customers request that any wrong URL of the same kind should give the same error page.

Note: I've tried with google.com and the result is worse even with just /a/a, so maybe the problem is not so important. :)

7
  • 2
    For the firth time I laugh about an error summary. Aug 8, 2013 at 21:01
  • :) Believe it or not but more than once they asked me to make these checks on some websites. Aug 8, 2013 at 21:03
  • 1
    Meh, who is doing this? And if they are, do we care?
    – Aaron Bertrand Staff
    Aug 8, 2013 at 21:09
  • Well, they want centralize the error controls, log everything inside the website environment, check unusual requests... things like that. Aug 8, 2013 at 21:14
  • I've posted it just as a curiosity, maybe it could be a hint for some user, who knows. Aug 8, 2013 at 21:15
  • Maybe because 31 is the most you can store in 5 bits?
    – Cole Tobin
    Aug 8, 2013 at 22:56
  • meta.stackoverflow.com/aa/aa/aa/aa/aa/aa/aa/aa/aa/aa/aa/aa/aa/… produces the same buggy result - this is clearly purely a result of the number of path components, not its length. Aug 8, 2013 at 23:00

0

You must log in to answer this question.

Browse other questions tagged .