X-PJAX is X-Pjax

[littke]

Hey.

Both Chrome dev and Firefox 4.0 seem to be converting the name of the header to X-Pjax, so looking for X-PJAX serverside didn't work for me.

[defunkt]

Are you sure this isn't your web framework? Firefox 4 on OS X is sending X-PJAX for me.

[littke]

FF 4.0.1 on Mac OS X 10.6.7: http://cl.ly/63Ek

Chrome dev says the same thing although admittedly the inspector doesn't allow me to look at a XHR atm.

[Zoramite]

Ubuntu 10.10 Chrome Dev shows this in the HAR output:

{"name":"X-Pjax","value":"true"}

[voxpelli]

HTTP Headers are case-insensitive according to the spec: http://www.rfc2616.com/#4.2 So this shouldn't be an issue - you should always check in a case-insensitive way anyway.

[littke]

Good point.

[defunkt]

Closing this unless someone thinks pjax should do something about it.

[littke]

I guess updating the documentation would be in order. I'll start handling it as lower case anyhow.

[huemorgan]

The back button (history) doesn't work when PJAX is on - I don't know if it's just a browser issue or
if it's not supported by PJAX - couldn't find an answer anywhere else.

I use Chrome 11.0.696.71 on Snow Leopard

[lotyrin]

@huemorgan: You're gonna want to file that as a different bug, because it is not related to this at all...

[Mstafamhamadmhamad]

Hey.

Both Chrome dev and Firefox 4.0 seem to be converting the name of the header to X-Pjax, so looking for X-PJAX serverside didn't work for me.