Bug 18528 - Spec is unclear about the case sensitivity of parameter values
Summary: Spec is unclear about the case sensitivity of parameter values
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: File API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Arun
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-10 16:11 UTC by Saurabh Anand
Modified: 2012-10-15 18:02 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Saurabh Anand 2012-08-10 16:11:29 UTC
http://tools.ietf.org/html/rfc2616#section-3.7 says that "Parameter values might or might not be case-sensitive,depending on the semantics of the parameter name".
Suppose, according to 4.B.b in http://dev.w3.org/2006/webapi/FileAPI/#slide-method-algo I convert every character in relativeContentType to lower case, while the parameter value was in upper case or mixed case and was case sensitive under the current semantics of the parameter name, then this would be a violation of http://tools.ietf.org/html/rfc2616#section-3.7 . http://tools.ietf.org/html/rfc2616#section-3.7 is used in 4.B.c.

I feel that 4.B.b and 4.B.c can conflict with http://tools.ietf.org/html/rfc2616#section-3.7 under the example I have given.

Expectation : Spec clearly defines the correct algorithm.
Comment 1 Arun 2012-10-15 18:02:25 UTC
We've decided to treat type as an opaque string.  Implementations don't throw; browser developers are reluctant to throw, and thus validation against the RFC is not useful.