Closed
Bug 375776
Opened 17 years ago
Closed 8 years ago
should set charset on submission's content type
Categories
(Core Graveyard :: XForms, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: aaronr, Assigned: aaronr)
Details
Attachments
(1 file)
1.73 KB,
application/xhtml+xml
|
Details |
Currently we don't put in the content type field (of the request header) what encoding we used for the submission body, even though we do put in the submitted xml document what the encoding type is. We should probably mimic Chiba and formsPlayer and do that. We've had a user already run into this issue and it was screwing up his servlet code.
Looks like charset can get set via SOAP, too. So if we blindly append charset like formsPlayer, for example, then there will be two charsets listed in the content type...one from the mediatype charset MIME parameter and one from the encoding attribute. I've asked the WG what should happpen: http://lists.w3.org/Archives/Public/www-forms/2007Mar/0060.html
Assignee: xforms → aaronr
Comment 3•8 years ago
|
||
RIP xforms
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•