The only header I've found you can't always set via xhr.setRequestHeader() is WWW-Authenticate because the browser thinks it should be responsible for HTTP Authentication. Which is why the last 2 optional arguments to xhr.open() are username and password, to effectively let you set these headers (it does the base64 encoding for you too which is handy).<br>
<br>If anyone manages to remember any specific browser limitations or can find any references please let me know since it would be important for any RESTful design.<br><br>Patrick<br><br><div class="gmail_quote">On Mon, May 5, 2008 at 9:34 PM, Matt S Trout <<a href="mailto:dbix-class@trout.me.uk">dbix-class@trout.me.uk</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Mon, May 05, 2008 at 10:46:56AM +0100, luke saunders wrote:<br>
> On Mon, May 5, 2008 at 1:20 AM, Patrick Donelan <<a href="mailto:pat@patspam.com">pat@patspam.com</a>> wrote:<br>
> ><br>
> > > No, but how you provide an alternative to full RESTness for clients that<br>
> > > don't handle the full range of HTTP verbs -is- a matter for discussion.<br>
> > ><br>
> ><br>
> > Which clients are we talking about here? I did a quick google search and<br>
> > could only find an off-hand remark along the lines of "in 2006 safari had<br>
> > poor support for REST verbs". I'm interested because in my own personal<br>
> > experience I haven't run into any problems generating PUT/POST/GET/DELETE<br>
> > with IE/FF/Opera browsers. Or are you talking about the inability to specify<br>
> > anything other than GET or POST as a form method?<br>
> ><br>
><br>
> I'm afraid I can't remember exactly, it was around two years ago and<br>
> we needed to fire PUT requests using XHR in JS using Dojo and it just<br>
> wasn't happening. Dojo has changed dramatically since then and now has<br>
> an xhrPut method so I expect whatever the problem has been addressed.<br>
<br>
</div>Doubt it.<br>
<br>
The problem was the browsers gleefully threw out half the headers we were<br>
trying to send when we used a PUT request. Fuck all dojo can do about that<br>
so far as I can see.<br>
<br>
Of course I forget which browsers and which headers, but it sure as hell<br>
fucked our shit up but good.<br>
<div class="Ih2E3d"><br>
--<br>
Matt S Trout Need help with your Catalyst or DBIx::Class project?<br>
Technical Director <a href="http://www.shadowcat.co.uk/catalyst/" target="_blank">http://www.shadowcat.co.uk/catalyst/</a><br>
Shadowcat Systems Ltd. Want a managed development or deployment platform?<br>
<a href="http://chainsawblues.vox.com/" target="_blank">http://chainsawblues.vox.com/</a> <a href="http://www.shadowcat.co.uk/servers/" target="_blank">http://www.shadowcat.co.uk/servers/</a><br>
<br>
_______________________________________________<br>
</div><div><div></div><div class="Wj3C7c">List: <a href="mailto:Catalyst@lists.scsys.co.uk">Catalyst@lists.scsys.co.uk</a><br>
Listinfo: <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst" target="_blank">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst</a><br>
Searchable archive: <a href="http://www.mail-archive.com/catalyst@lists.scsys.co.uk/" target="_blank">http://www.mail-archive.com/catalyst@lists.scsys.co.uk/</a><br>
Dev site: <a href="http://dev.catalyst.perl.org/" target="_blank">http://dev.catalyst.perl.org/</a><br>
</div></div></blockquote></div><br>