From Bugzilla Helper: User-Agent: Mozilla/4.73 [en] (X11; I; Linux 2.2.14-5.0 i586; Nav) BuildID: Mozilla/5.0 (X11; U; Linux 2.2.14-5.0 i586; en-US; m17) Gecko/20000721 Occationally, Mozilla seems to send incorrect GET requests. This is from my apache access_log while trying to view my web page: 128.2.85.113 - - [24/Jul/2000:09:50:00 -0400] "GET /~jgajnak HTTP/1.1" 301 326 128.2.85.113 - - [24/Jul/2000:09:50:01 -0400] "GET /~jgajnak/ HTTP/1.1" 200 214 128.2.85.113 - - [24/Jul/2000:09:50:03 -0400] "GET /~jgajnak/title.html HTTP/1.1" 200 715 128.2.85.113 - - [24/Jul/2000:09:50:03 -0400] "GET /~jgajnak/home.html HTTP/1.1" 200 4370 128.2.85.113 - - [24/Jul/2000:09:50:06 -0400] "GET http://verbal.rem.cmu.edu/~jgajnak/images/cs_major.jpg HTTP/1.1" 404 322 In the case of the last line, its including the entire URL, not the server-based locale. Reproducible: Sometimes Steps to Reproduce: 1. Go to some http://verbal.rem.cmu.edu/~jgajnak/ Actual Results: the picture, cs_major.jpg never is displayed. The images is there, and is properly show in both NS 4.73 and IE 5.5. Expected Results: It should be sending "GET /blah_blah_blah/x.jpg" instead of "GET http://someserver.com/blah_blah_blah/x.jpg"

wfm in 072408 winnt. May be Linux problem. Leaving unconfirmed.

Please read the HTTP/1.0 and HTTP/1.1 RFC: http://www.rfc-editor.org/rfc/rfc1945.txt http://www.rfc-editor.org/rfc/rfc2068.txt For both versions of HTTP this is a perfectly valid HTTP request, from section 5.1.2 of RFC 2068: The Request-URI is a Uniform Resource Identifier (section 3.2) and identifies the resource upon which to apply the request. Request-URI = "*" | absoluteURI | abs_path The three options for Request-URI are dependent on the nature of the request. The asterisk "*" means that the request does not apply to a particular resource, but to the server itself, and is only allowed when the method used does not necessarily apply to a resource. One example would be OPTIONS * HTTP/1.1 The absoluteURI form is required when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache, and return the response. Note that the proxy MAY forward the request on to another proxy or directly to the server specified by the absoluteURI. In order to avoid request loops, a proxy MUST be able to recognize all of its server names, including any aliases, local variations, and the numeric IP address. An example Request-Line would be: GET http://www.w3.org/pub/WWW/TheProject.html HTTP/1.1 To allow for transition to absoluteURIs in all requests in future versions of HTTP, all HTTP/1.1 servers MUST accept the absoluteURI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies. The problem here is that mozilla is trying to request this page from a proxy, not that it is generating invalid requests. Changing component to Networking and updating Summary

wfm on linux CVS from 07/31. can you recheck this?

wfm on linux 2000080308. Of course, I can't see the HTTP transaction going on, but i assume the problem is that he was using a proxy that let an absulute URI slip by rather then proccess it. Leaving unconfirmed for now, requesting someone from networking to comment/confirm/resolve.

How does the picture not displaying relate to the behaviour or proxies? I have no idea what is going on here, but I would like to boot this off unconfirmed

jgajnak@andrew.cmu.edu - are you using a proxy and, if so, what sort? Gerv

Yeah, I was using junkbuster...sorry I haven't had time to check a nightly against it recently.

Assigning to Networking owner. When changing components on un-triaged bugs, please reassign.

I think this is a dup of bug 38488.

agreed, looks like bug 38488 *** This bug has been marked as a duplicate of 38488 ***

Verified dupe.

Mass removing self from CC list.

Now I feel sumb because I have to add back. Sorry for the spam.