Hi, You can file a bug report here: https://prototype.lighthouseapp.com/projects/8886/home
If I understand you correctly, what you're saying is that when looking for an *existing* Content-Type header, Prototype should do the check without case sensitivity. It's best to put together a small, self-contained example demonstrating the bug, and of course, if you have the time and skills to post a patch along with the bug report... (But that's *not* necessary.) -- T.J. Crowder Independent Software Engineer tj / crowder software / com www / crowder software / com On Feb 24, 1:32 am, Peter <[email protected]> wrote: > Hi. There are a few references to Content-type in prototype.js. > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.htmlmentions: > Field names are case-insensitive. > > This causes an issue. > > I am setting a Content-Type. > > Prototype then tacks on an extra Content-type header. > > Instead I'd recommend it just used the regular Content-Type name > perhttp://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17 > > - Peter -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
