- From: <bugzilla@jessica.w3.org>
- Date: Fri, 10 Aug 2012 16:11:30 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18528
Summary: Spec is unclear about the case sensitivity of
parameter values
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: File API
AssignedTo: arun@mozilla.com
ReportedBy: saurabhanandiit@gmail.com
QAContact: public-webapps-bugzilla@w3.org
CC: public-webapps@w3.org
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.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 10 August 2012 16:11:32 UTC