For more on the query string take a look at <http://jakarta.apache.org/commons/httpclient/apidocs/org/apache/commons/httpclient/HttpMethodBase.html#setQueryString(org.apache.commons.httpclient.NameValuePair[])>
In the case of authentication it is a little more complicated, as it depends on the authentication method. Basic authentication uses ISO-8859-1 for username and password. Digest uses ISO-8859-1 for username and password, but the username can really only be in ASCII, since it is passed as plain text in the header. NTLM only supports ASCII.
Mike
Sven Köhler wrote:
nun habe ich noch das problem das er kein Dateien mit umlauten versenden kann,z.b Übung1.txt
I guess you're talking about the content-disposition header or http-headers with umlauts in general - i think there's no standard for sending them.
First, i have to define a http-header to be more like a byte[]-array than a String (in the Java sence). The bytes will have to be interpretated by a Charset like UTF8, ISO8859-1 etc. to become a String on the client-side. MaxOSX might use UTF8, Linux and Windows should use the current locale. So there is no correct way to store a umlaut in a HTTP-header since HttpClient cannot know the Charset that the client will use.
The Charset for the Headers and the Charset used for the URL are one of the weaknesses of the HTTP-Protocol. UTF8 may become a standard - but this will surely take a while.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
