> "hashbang" URLs (they call them Escaped Fragment URLs)
why not use the RFC terms? https://tools.ietf.org/html/rfc3986#section-3 "url fragment"
Also, it won't help you on server side rendering since the server will never even see it on the request.
why not use the RFC terms? https://tools.ietf.org/html/rfc3986#section-3 "url fragment"
Also, it won't help you on server side rendering since the server will never even see it on the request.
Because it's specifically different, on purpose. The RFC doesn't cover the "bang" part....the "!".
>>the server will never even see it on the request
Explained on the (now deprecated) page from Google on this "hashbang" approach:
*"The answer is the URL that is requested by the crawler: the crawler will modify each AJAX URL such as www.example.com/ajax.html#!key=value to temporarily become www.example.com/ajax.html?_escaped_fragment_=key=value"
It will when Googlebot sees the link and rewrites the URL.