Getting an Error #2032: Stream Error with a Flex app running on Chrome only <p>I'm having a crazy error when I run my Flex application on Chrome when the server HTTP response it's an Internal Server Error (500) only. It works perfectly on Firefox and IE.</p> <p>Using Fiddler, I know the server is giving the correct response. An 500 error with short XML data content holding the error message:</p> <p>HEADER:</p> <p>HTTP/1.1 500 LoginFailedException</p> <p>Cache-Control: private</p> <p>Content-Type: application/xml</p> <p>Server: Microsoft-IIS/7.5</p> <p>X-Powered-By: ServiceStack/3.85 Win32NT/.NET</p> <p>X-AspNet-Version: 4.0.30319</p> <p>X-Powered-By: ASP.NET</p> <p>Content-Length: 319</p> <p>DATA:</p> <pre><code>&lt;LoginDtoResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.servicestack.net/types"&gt;&lt;ResponseStatus&gt;&lt;ErrorCode&gt;V2LoginFailedException&lt;/ErrorCode&gt;&lt;Errors /&gt;&lt;Message&gt;Invalid username or password. Please try again.&lt;/Message&gt;&lt;StackTrace i:nil="true" /&gt;&lt;/ResponseStatus&gt;&lt;/LoginDtoResponse&gt; </code></pre> <p>But back to Chrome the response is totally missing, I'm getting this: </p> <blockquote> <p>HTTP request error Server.Error.Request Error #2032: Stream Error</p> </blockquote> <p>Using Flex RPC HTTPService, I've tried changing the call headers and this is how I'm making the calls (GET and POST):</p> <pre><code>httpService = new HTTPService(); httpService.resultFormat = "e4x"; httpService.concurrency = "single"; httpService.requestTimeout = 90; httpService.useProxy = false; httpService.headers["pragma"] = "public"; httpService.headers["DNT"] = "1"; httpService.headers["Cache-Control"] = "no-store"; </code></pre> <p>The system has a crossdomain.xml, I verified and it seems to be OK.</p> <p>Also I've tried changing the Chrome Flash plugin with the Abobe Flash plugin with no results</p> <p><img src="https://i.stack.imgur.com/7L23y.png" alt="enter image description here"></p> <p>And of course tried google it (spent day and half in fact) and it seems it used to happen a long time ago with IE 7, but never with Chrome. </p> <p>Clearly something dodgy is going on, and it's driving me crazy! Please, any advice is welcome. </p> <p>Thanks a lot!</p>