Sebb, thanks again for the advices. I have compared headers and requests with diff applications, but the only difference i get its the orden in headers' list and the type of connection, which in jmeter is "keep-alive" and in any browser is "Keep-Alive" (the case letters). Also i have tried with RAW request from Jmeter, but i dont know how to handle keep-alive connections with this plugin and the request keeps connected until is disc from server, throwing error, and i cant see what jmeter received.
I have captured the same test with blazemeter, and different browsers (Chrome, Safari, firefox) and even jmeter over several SO (os mavericks x64, Windows xp x32, windows 7 x32, Linux redhat x32), but the results are always the same. I have checked some metabase properties at IIS 6.0 for handling HTTP compression, but it doesn't have Any compression enabled except for on-demand compression. I disabled it, but anything happened. Does IIS http compression sends incomplete HTML data with "tags" with reference to another page at the end of every chunk that the browser needs to process in orden to complete the HTML page with the next chunk of data? Im lost here. Anyway, meanwhile Im using another testing tool with the same headers and request data and works fine. Im gonna post my headers and request with the Sample of the responses so you could find something i have not able to do so, if the only way to the solution to my problem is headers and request. Best regards, Enrique Guadalupe -- View this message in context: http://jmeter.512774.n5.nabble.com/HTTPS-IIS-COMPRESSION-and-JMeter-tp5719160p5719189.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
