Quantcast
Channel: General
Viewing all articles
Browse latest Browse all 7363

Handling invalid Accept-Encoding HTTP Headers

$
0
0

Hi

We have a Web Service deployed with ASP.NET in IIS. All worked well until we installed Windows Server 2008 R2 & IIS 7.5.

We have one trading partner who is sending invalid Accept-Encoding HTTP Headers. For IIS 6 & 7 their transmissions work and for IIS 7.5 they are rejected with: the message:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>Bad Request</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD><BODY><h2>Bad Request</h2> <hr><p>HTTP Error 400. The request is badly formed.</p> </BODY></HTML>

The trading partner are unable to change their Web Service client to stop sending the invalid values. and we are prevented form deploying current versions of Windows Server, which is becoming increasingly difficult to avoid.

Is there a way to convince IIS 7.5 to accept the invalid values (like earlier IIS versions)?

The HTTP Header value is:  Accept-Encoding:  gzip, application/soap+xml, application/xml, text/xml

See my earlier post that describes the problem: http://forums.iis.net/p/1176719/1976080.aspx

 

Thanks

Steve

 


Viewing all articles
Browse latest Browse all 7363

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>