18528 2012-08-10 16:11:29 +0000 Spec is unclear about the case sensitivity of parameter values 2012-10-15 18:02:25 +0000 1 1 1 Unclassified WebAppsWG File API unspecified All All RESOLVED FIXED P2 normal --- 1 saurabhanandiit arun Ms2ger public-webapps public-webapps-bugzilla oldest_to_newest 72046 0 saurabhanandiit 2012-08-10 16:11:29 +0000 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. 76320 1 arun 2012-10-15 18:02:25 +0000 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.