[ https://issues.apache.org/jira/browse/HARMONY-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835355#action_12835355
]
Elliott Hughes commented on HARMONY-6452:
-----------------------------------------
see also http://code.google.com/p/android/issues/detail?id=6684. i've fixed the case problem
in Android, but still need to fill out the Apache paperwork.
the submitter didn't give an example of "each property-value can only contain one entry" which,
unlike the case problem, isn't obviously true.
> HttpUrlConnection converts request headers to lowercase - HttpUrlConnection.addRequestProperty
overrides existing properties
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-6452
> URL: https://issues.apache.org/jira/browse/HARMONY-6452
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: Android 1.6
> Reporter: Michael Andresen
> Assignee: Mark Hindess
>
> Problem: Lower-Case-Headers
> ==============================
> In Sun's JRE this code
> java.net.HttpURLConnection conn = (java.net.HttpURLConnection)(new java.net.URL("http://...").openConnection());
> conn.setRequestProperty("Content-Type", "multipart/form-data; boundary=...");
> System.out.println (conn.getRequestProperty("content-type"));
> System.out.println (conn.getRequestProperties());
> produces the following output:
> multipart/form-data; boundary=...
> {Content-Type=[multipart/form-data; boundary=...]}
> The Property-Name "Content-Type" is stored case sensitive but it can be fetched in lower-case.
> The resulting Request-Header sent to the Web-Server is case sensitive.
> On Android 1.6 (which uses Apache Harmony) the same Code produces the following output:
> multipart/form-data; boundary=...
> {content-type=[multipart/form-data; boundary=...]}
> This time the Property-Name "Content-Type" is stored in lower-case. The resulting Request-Header
is also sent in lower-case. That's a violation of the HTTP 1.1 spec, and certain service providers
may ignore such Request-Headers.
> In harmony 5.0 r901653 the output is the same as on Android 1.6 but the resulting Request-Header
is sent case-sensitive.
> Problem addRequestProperty overrides existing properties
> ==============================================
> Existing Properties should be appended.
> Info
> ==============================================
> The class org.apache.harmony.luni.internal.net.www.protocol.http.Header is not correct
implemented. It only works with lower-case property-names and each property-value can only
contain one entry.
> Question
> ==============================
> 1. Does anybody know how to find out which version of harmony is used by Android 1.6?
I tried System.getProperties() but that didn't help.
> 2. I would like to attach a patch to this issue but I don't know how? Simply copy it
into the Description? Is there a File-Upload?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|