You can file a bug report here:
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*
Independent Software Engineer
tj / crowder software / com
www / crowder software / com
On Feb 24, 1:32 am, Peter <p.google....@rimuhosting.com> wrote:
> Hi. There are a few references to Content-type in prototype.js.
> 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
> - 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@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at