Takahashi-san,

Ah sorry misunderstood which part your were talking about. I assume wrongly you were talking about navigation. 

Yes for the request which is sent to the server it should be
http://tools.ietf.org/html/rfc7230#section-5.3.1
So refactoring your example.

1st request:

    GET /foo HTTP/1.1
    Accept: text/html
    Host: example.com

server response
    HTTP/1.1 302 Found
    Location: /bar#test

second request must be
    GET /bar HTTP/1.1
    Accept: text/html
    Host: example.com

As for the navigation context is indeed part of the piece of code taking in charge the document after being parsed and not the one doing the HTTP request. (putting it here just that people understand)


(to be tested)
For server side receiving invalid Request-line 
http://tools.ietf.org/html/rfc7230#section-3.1.1

   Recipients of an invalid request-line SHOULD respond with either a
   400 (Bad Request) error or a 301 (Moved Permanently) redirect with
   the request-target properly encoded.  A recipient SHOULD NOT attempt
   to autocorrect and then process the request without a redirect, since
   the invalid request-line might be deliberately crafted to bypass
   security filters along the request chain.