There's a good chance that you simply haven't found the correct combination of header values yet for that web server.
First of all, why would you use this? Accept-Encoding: * That tells the server that ANY encoding is valid. In theory, the most restrictive "Accept-Encoding" header would be: Accept-Encoding: *;q=0 That should indicated that ALL forms (except "identity" of course). If you really wanted, you could do: Accept-Encoding: *;q=0, identity;q=1 Read up here: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.3 http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.39 ~Brad -------- Original Message -------- Subject: Re: cfhttp Connection Failure From: Sue Buck <sue.b...@avsi.co.uk> Date: Tue, April 20, 2010 8:20 am To: cf-talk <cf-talk@houseoffusion.com> Thanks for all the suggestions. Unfortunately my client is phasing out ColdFusion so upgrading is not an option. I've installed Wireshark and using <cfhttpparam type="Header" name="Accept-Encoding" value="*"> <cfhttpparam type="Header" name="TE" value="deflate;q=0"> get the same headers as shown in the brook-bilson example with CF 8.0.1 with no CHF (which in the example returned the data uncompressed) but the headers show that I'm still getting the data back compressed. Do you think that the laterooms server is ignoring the TE header? I also looked at the headers using the java.net.URL approach and it does not send an Accept-Encoding or a TE header just an Accept header. I've tried imitating this but the cfhttp tag always adds Accept-Encoding and TE headers. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:333039 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
