Can Java Servlets Access the Request's URL Fragment Identifier

Question

As per RFC 1808 section 2.4.1 (if that is the right one to reference here):
"If the parse string contains a crosshatch "#" character, then the substring after the first (left-most) crosshatch "#" and up to the end of the parse string is the <fragment> identifier. If the crosshatch is the last character, or no crosshatch is present, then the fragment identifier is empty. The matched substring, including the crosshatch character, is removed from the parse string before continuing.
Note that the fragment identifier is not considered part of the URL. However, since it is often attached to the URL, parsers must be able to recognize and set aside fragment identifiers as part of the process."
I've noticed using Servlets, that I cannot get the fragment identifier that was used in the incoming URL. Is this intentional? And if so, where is that defined in the Servlet spec or documentation? If not, what is the appropriate way to get the fragment identifier from the incoming request?
I have noticed that when I send a redirect from a Servlet, that the fragment identifier ends up on the destination URL when the redirect is followed by a browser. But, absent a packet tracer at the moment, this, I believe, is the browser's doing and wasn't part of the Servlet's response.

Answer 1

Clear the cache and the cookies from sites that cause problems.
* "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
* "Remove the Cookies" from sites causing problems: Tools > Options > Privacy > Cookies: "Show Cookies"
* http://kb.mozillazine.org/The_page_is_not_redirecting_properly