You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Alexandre Mazouz <al...@gmail.com> on 2008/08/01 17:31:37 UTC
Re: Firefox 3 and URL
Hello,
After a lot of debugging and other things, i have found a new problem with
FF3.
In FF2, IE6, IE7 it works fine but not in FF3.
*******************************
if (!this.xmlHttp) {
this.xmlHttp = Sarissa.getXmlHttpRequest();
}
this.xmlHttp.open("HEAD", resourceName, false);
this.xmlHttp.send(null);
return (this.xmlHttp.status == 200 && this.xmlHttp.responseXML);
*******************************
the resourceName is "/dy/browse/bv/nr500/nr500_2008/loc/n0001.xml".
the statusText is "OK" and status 200.
i have no responseXML.
something seems strange is that when the this.xmlHttp.open is done, i have
the this.xmlHttp.statusText=this.xmlHttp.channel
all seems to be fine but i get nothing in FF3 (responseXML=null).
Is there any idea from where is the problem and how to fix it?
Thanks,
Alexandre
Alexandre Mazouz wrote:
>
> Thanks for your help,
>
> I have advanced in my debug job but not finished.
>
> I will try to redeclare functions of a core librairies.
>
>
> Joerg Heinicke wrote:
>>
>> In Javascript you can use prototype to redeclare functions of an object.
>> I wonder if it works though with core libraries or if they aren't locked.
>>
>> Joerg
>>
>> On 02.07.2008 08:48, Luca Morandini wrote:
>>
>>>> i have : xElt.getElementsByTagName(...);
>>>>
>>>> xElt is a XMLElement.
>>>>
>>>> i want to use your function instead of getElementsByTagName but i
>>>> don't know
>>>> how can i make it.
>>>
>>> Hmm... as I see it, there is only one way: change every instance of
>>> xElt.getElementsByTagName("pipeline") to getElementsByTagNameNoNS(xElt,
>>> "pipeline", "map") either manually or using your editor of choice
>>> search&replace.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Firefox-3-and-URL-tp18212745p18777088.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Firefox 3 and URL
Posted by Alexandre Mazouz <al...@gmail.com>.
I use the plugin Firebug to debug my web application.
I understand that Head request do not send response but Firebug shows me
something else in FF2.
I use Cocoon 2.1.7/Jetty/sarissa 0.9.4.4.
Thanks,
Alexandre
Andy Stevens-2 wrote:
>
> 2008/8/4 Alexandre Mazouz <al...@gmail.com>:
>>
>> Okay,
>>
>> My problem is now fixed.
>>
>> Instead of using HEAD request, i have used GET request :
>>
>> this.xmlHttp.open("GET", resourceName, false);
>> this.xmlHttp.send(null);
>>
>> I think that Firefox 2.0 and Firefox 3.0 have different behaviour of how
>> to
>> handle request.
>>
>> For FF3
>> *In the case of this.xmlHttp.open("HEAD", resourceName, false); : i have
>> no
>> responseXML (null)
>> *In the case of this.xmlHttp.open("GET", resourceName, false); : i have
>> responseXML
>>
>> For FF2
>> *In the case of this.xmlHttp.open("HEAD", resourceName, false); : i have
>> responseXML
>> *In the case of this.xmlHttp.open("GET", resourceName, false); : i have
>> responseXML
>>
>> Why this different behavior?
>
> Given the point of a HEAD request is to fetch the response headers
> without the actual body [1], I'm surprised you expected responseXML to
> contain anything in the first place. Are you sure the XHR
> open("HEAD", ...) in FF2 is actually sending a HEAD and not using a
> GET anyway? It could be that version doesn't support HEAD and falls
> back on the other method, and they've improved things by v3. I'd be
> tempted to try a packet sniffer or the Live HTTP Headers extension to
> see exactly what gets sent & received. Also check the web server
> access logs to see what method it thinks was used in each case. I'd
> be surprised if the server responded differently to HEAD requests
> according to the browser version, returning the content body in one
> case and not the other. What server software are you using anyway?
>
>
> Andy.
> [1] http://en.wikipedia.org/wiki/HTTP_HEAD_request#Request_methods
> --
> http://pseudoq.sourceforge.net/ Open source java Sudoku application
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Firefox-3-and-URL-tp18212745p18810281.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Firefox 3 and URL
Posted by Andy Stevens <in...@googlemail.com>.
2008/8/4 Alexandre Mazouz <al...@gmail.com>:
>
> Okay,
>
> My problem is now fixed.
>
> Instead of using HEAD request, i have used GET request :
>
> this.xmlHttp.open("GET", resourceName, false);
> this.xmlHttp.send(null);
>
> I think that Firefox 2.0 and Firefox 3.0 have different behaviour of how to
> handle request.
>
> For FF3
> *In the case of this.xmlHttp.open("HEAD", resourceName, false); : i have no
> responseXML (null)
> *In the case of this.xmlHttp.open("GET", resourceName, false); : i have
> responseXML
>
> For FF2
> *In the case of this.xmlHttp.open("HEAD", resourceName, false); : i have
> responseXML
> *In the case of this.xmlHttp.open("GET", resourceName, false); : i have
> responseXML
>
> Why this different behavior?
Given the point of a HEAD request is to fetch the response headers
without the actual body [1], I'm surprised you expected responseXML to
contain anything in the first place. Are you sure the XHR
open("HEAD", ...) in FF2 is actually sending a HEAD and not using a
GET anyway? It could be that version doesn't support HEAD and falls
back on the other method, and they've improved things by v3. I'd be
tempted to try a packet sniffer or the Live HTTP Headers extension to
see exactly what gets sent & received. Also check the web server
access logs to see what method it thinks was used in each case. I'd
be surprised if the server responded differently to HEAD requests
according to the browser version, returning the content body in one
case and not the other. What server software are you using anyway?
Andy.
[1] http://en.wikipedia.org/wiki/HTTP_HEAD_request#Request_methods
--
http://pseudoq.sourceforge.net/ Open source java Sudoku application
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Firefox 3 and URL
Posted by Alexandre Mazouz <al...@gmail.com>.
Okay,
My problem is now fixed.
Instead of using HEAD request, i have used GET request :
this.xmlHttp.open("GET", resourceName, false);
this.xmlHttp.send(null);
I think that Firefox 2.0 and Firefox 3.0 have different behaviour of how to
handle request.
For FF3
*In the case of this.xmlHttp.open("HEAD", resourceName, false); : i have no
responseXML (null)
*In the case of this.xmlHttp.open("GET", resourceName, false); : i have
responseXML
For FF2
*In the case of this.xmlHttp.open("HEAD", resourceName, false); : i have
responseXML
*In the case of this.xmlHttp.open("GET", resourceName, false); : i have
responseXML
Why this different behavior?
Thanks,
Alexandre
Alexandre Mazouz wrote:
>
> Hello,
>
> After a lot of debugging and other things, i have found a new problem with
> FF3.
> In FF2, IE6, IE7 it works fine but not in FF3.
>
> *******************************
> if (!this.xmlHttp) {
> this.xmlHttp = Sarissa.getXmlHttpRequest();
> }
> this.xmlHttp.open("HEAD", resourceName, false);
> this.xmlHttp.send(null);
> return (this.xmlHttp.status == 200 && this.xmlHttp.responseXML);
> *******************************
> the resourceName is "/dy/browse/bv/nr500/nr500_2008/loc/n0001.xml".
> the statusText is "OK" and status 200.
>
> i have no responseXML.
>
> something seems strange is that when the this.xmlHttp.open is done, i have
> the this.xmlHttp.statusText=this.xmlHttp.channel
>
> all seems to be fine but i get nothing in FF3 (responseXML=null).
>
> Is there any idea from where is the problem and how to fix it?
>
> Thanks,
> Alexandre
>
>
--
View this message in context: http://www.nabble.com/Firefox-3-and-URL-tp18212745p18809075.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org