Is there a length limit for the fragment part of an URL (also known as the hash)?
-
There is no standard for the hash as it is client-side only, but the limit is generally [very high](http://stackoverflow.com/a/25759637/405550). – Zaz Feb 03 '17 at 21:06
3 Answers
The hash is client side only, so the rules for HTTP may not apply to it.

- 34,230
- 18
- 50
- 51
-
3The "hash" is actually the URL Fragment and is not sent to the server, hence the length limitation from a server perspective doesn't apply. – Sai Dubbaka Nov 10 '17 at 03:23
It depends on the browser. I found that in safari, chrome, and Firefox, an URL with a long hash is legal, but if it is a param send to the server, the browser will display an 414 or 413 error.
for example:
an URL like http://www.stackoverflow.com/?abc#{hash value with 100 thousand characters}
will be ok. and you can use location.hash to get the hash value in javascript but an URL like http://www.stackoverflow.com/?abc&{query with 100 thousand characters}
will be illegal, if you paste this link in the address bar, a 413 error code will be given and the message is the client issued a request that was too long
. If that is a link in a web page, in my computer, Nginx response the 414 error message.
I don't know the situation in IE.
So I think, the limitation of the length of URL is just for transmission or HTTP server, the browser will check it sometimes, but not every time, and it will always be allowed to be used as a hash.

- 971
- 9
- 22
-
2Did you find any official (docs) information regarding the client side limitations (or lack thereof)? – Moshe Jonathan Gordon Radian Nov 01 '20 at 14:06
-
10RFC2616 doesn't mention fragments except to say: "The URI MUST NOT include a fragment" – Rick Jan 11 '17 at 19:13
-
8
-
1