completely right now... have to talk to my ISP about that.
The problem is that if compression is enabled for applications and/or static
content in IIS, Java clients can't decompress the content, including the
ColdFusion server. There seems to be a compatibility problem with the
compression algorithms used (I assume).
The solution or workaround is to add two headers to the request using
CFHTTPPARAM where the values for those headers include a "quality factor"
described in the HTTP 1.1 RFC, if I recall correctly. The quality factor is
set with a numeric value from 0 to 100, where 0 indicates the least
preference for the Header context. Using the headers with this quality
factor (;q=0) is like telling the webserver that you prefer that it not
compress the content of the HTTP Response.
The headers to include are:
<cfhttpparam type="Header" name="Accept-Encoding" value="deflate;q=0">
<cfhttpparam type="Header" name="TE" value="deflate;q=0">
This way the IIS webserver continues to compress output for all requests,
except those requests that specify a preference to receive uncompressed
content.
I don't know exactly why Java clients can't decompress the IIS compressed
content, but I'd be interested to know if anyone can elaborate on that.
-Steve
_____
From: Tony Weeg [mailto:[EMAIL PROTECTED]
Sent: Friday, August 20, 2004 9:57 AM
To: CF-Talk
Subject: Re: connection failure cfhttp
thanks dave, but i figured it out, after i read this on steven erat's
blog...
i was hitting an iis6 box, and it has some sort of auto-compression
type stuff...anyway, got it!
thanks.
http://www.talkingtree.com/blog/index.cfm?data="">
tw
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
