hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Magnus Gustavsson (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HTTPCLIENT-1185) IIS and fragments in "Location:" headers
Date Fri, 20 Apr 2012 13:44:43 GMT
IIS and fragments in "Location:" headers

                 Key: HTTPCLIENT-1185
                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1185
             Project: HttpComponents HttpClient
          Issue Type: Bug
          Components: HttpClient
    Affects Versions: 4.1.3
            Reporter: Magnus Gustavsson

We're using HttpClient to check the validity of links on our site, and lately users have been
reporting that working links are incorrectly flagged as invalid. Looking into the problem,
I find that it all boils down to us using code somewhat like this:

import java.io.IOException;
import org.apache.http.client.HttpClient;
import org.apache.http.client.methods.HttpGet;
import org.apache.http.impl.client.DefaultHttpClient;

public class BadRequest {
    public static void main(String[] args) {
	try {
	    HttpClient httpclient = new DefaultHttpClient();
	    HttpGet httpget = new HttpGet("http://www.edu.mah.se/KK3231/syllabus/");
	} catch (IOException e) {

Compiling and running the above example with HttpClient 4.1.3 results in a 400 code (20 April
in 2012).

Specifically in the following exchanges:

GET /KK3231/syllabus/ HTTP/1.1
Host: www.edu.mah.se
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.3 (java 1.5)

HTTP/1.1 301 Moved Permanently
Content-Type: text/html; charset=UTF-8
Location: http://edu.mah.se/sv/Course/KK3231#Syllabus
Server: Microsoft-IIS/7.5
X-Powered-By: PHP/5.3.9
X-Powered-By: ASP.NET
Date: Fri, 20 Apr 2012 12:33:40 GMT
Content-Length: 315

GET /sv/Course/KK3231#Syllabus HTTP/1.1
Host: edu.mah.se
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.3 (java 1.5)

HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Fri, 20 Apr 2012 12:33:40 GMT
Connection: close
Content-Length: 324

I do realize that according to the HTTP 1.1 standard, the location header returned by the
server is invalid.

However, all browsers seem to be able to handle a redirection like this. Thus I can hardly
tell users that the error is on the server side when they can paste it into any browser and
get a working page. So I was wondering if you would consider adapting to the current state
of things and perhaps strip fragments from redirect URIs?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message