Closed Bug 238144 Opened 20 years ago Closed 8 years ago

The XMLHttpRequest object doesn't save the request type if there's an http redirection

Categories

(Core :: XML, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: javier, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

I'm trying to implement httpmail(the outlook->hotmail "protocol") in xul, and i
need to send a request to "http://services.msn.com/svcs/hotmail/httpmail.asp"
but the method isn't a get or a post, it's a 'PROPFIND'
the problem is that the first site redirects to some other site, and then the
object doesn't send the correct method, it send "get" instead of the one i told him

Reproducible: Always
Steps to Reproduce:
1. create an XMLHttpRequest object
2. tell it to open "http://services.msn.com/svcs/hotmail/httpmail.asp" with the
metod "propfind"


Actual Results:  
wait and it'll tell you 'incorrect request' or something like that, not the
object, the website
if you use some kind of network sniffer you'll see that th request method is
changed after the first redirect

Expected Results:  
the request method should be the same every time
i've just notted that it doen't even save the headers added with "setRequestHeader"
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
I may be seeing this. Assumably you have to have (or create) a Hotmail account
to test. Then, when the auth dialog comes up, type in your email address and
password. After that point I see 302 redirect and the next command Mozilla
issues is GET. I get login failed error after that. I haven't tried if it would
work if I made that be PROPFIND.

What do other clients do - IE, Safari and Opera now all support XMLHttpRequest
to some level?
Assignee: dougt → xml
Component: XPCOM → XML
QA Contact: ashshbhatt
I can confirm this bug. The W3C states that the XHR object should handle redirects "transparently". The current behaviour in Firefox (2.0.0.3) is to ignore whatever headers were sent in the initial request and use the default firefox request headers to retrieve the url that the XHR object has been redirected to. This is not "transparent" in my book. 

IE7 appears to handle this correctly.

To replicate this bug simply try creating an XHR object and get a url that issues a redirect. Using a tool like Firebug should show clearly the difference in the request headers between the original request and the request for the redirected url.
Assignee: xml → nobody
QA Contact: ashshbhatt → xml
This bug no longer reproduces. I just double-checked that Firefox forwards the method and headers during XHR redirects.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.