tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eirik √ėverby <>
Subject Content-Type rewriting in jakarta-tomcat-connectors
Date Wed, 01 Dec 2004 17:45:25 GMT

After upgrading from tomcat 4.1 to 5.0, a critical application here has
stopped working as expected. Upon replying to incoming requests, it
would usually spit out the following - just like the servlet says:

Content-Type: application/xml; charset=utf-8

In 5.0.29, this comes out as

Content-Type: application/xml;charset=utf-8

In the second variant, the space between the ; and the charset string is
gone. This breaks a *very* important service that we provide for a
rather large credit card company.

Without having studied RFCs and so on, I am pretty certain that it would
be good coding-etiquette to have your app accept a Content-Type string
with or without that space. Yes, I therefore know, it's their server -
which sends the request to us - that has a lousy implementation.

However, the key here is that the connector (more specifically around
line 520 in
is rewriting the carefully-constructed Content-Type string in a way that
1: I didn't ask for and 2: wasn't done in 4.1.

Given that it is highly unlikely that anyone "at the other end" is going
to do anything about this any time soon, and given that the solution is
very trivial (add a space in that string composer in, how
are the chances of seeing this 'fixed' in an upcoming release of Tomcat

I really would rather not have to maintain my own source for Tomcat -
I've spent the better part of the last 6 months trying to wrestle the
application we are running out of a customized environment and into a
standardized one; this would go head-on with that effort.. :(

Thanks for listening,

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message