EVALUATION
###@###.### 2003-01-21
The "text/html" is returned from java.net.URLConnection.guessContentTypeFromStream. Based on the comments of this method, I guess the proxy server crowroad.eng does not return the correct content type. Reassign to Networking team for further investigation.
--
A snoop reveals that when using the crowroad.eng proxy the POST command sent is
POST http://suntea.central.sun.com:-1/servlet/SunTEAServlet HTTP/1.1
instead of
POST /servlet/SunTEAServlet HTTP/1.1
when accessing directly to suntea.central.
-1 means default port and is accepted by most proxies (scaweb.sfbay does for instance). I'm unsure at this point whether this is a bug in Squid or something we should fix.
###@###.### 2003-01-21
It seems suntea is creating an illegal URL (puting a -1 as port number). The reason it was not a problem before was because of another bug (4720715) which was masking this one.
The issue is that some proxies do accept URLs with a port number of -1, while others don't.
It could be seen as a compatibility problem, and a workaround is not too complicated (see suggested fix), but it is unclear how serious a problem it is since the URL has to be created incorrectly to begin with.
###@###.### 2003-01-23
The URL in question is created using the single argument constructor
as follows: new URL ("http://suntea.central:-1/servlet/and_so_on");
This constructor is supposed to take a URL formatted as defined in
RFC2396. The URL should look like "http://suntea.central/servlet/and_so_on"
ie. the :port number notation is necessary when the default port should
be used, and as RFC2396 states, a negative value is not allowed.
###@###.### 2003-01-23
Closing as "not a bug".
###@###.### 2003-05-13