Forum Discussion
Gerardo_Garcia_
Nimbostratus
NimbostratusActive X not loading ojects when chuncked
We implemented SSL for our external users and along with that we included rechunking to recalculate the size of the page for the external users.
Since we implement this change in our environment some ActiveX loading some files are not working any more.
When we access those files directly they work fine when we access them through BIG IP they don't work.
If you compare the two outputs this is what you will see in the headers for these objects.
Is there any way to fix this for the user?
HTTP/1.1 206 Partial ContentHTTP/1.1 200 OK
Content-Type: application/octet-streamContent-Type: application/octet-stream
Content-Length: 579972
Content-Range: bytes 0-579971/579972
Accept-Ranges: bytes
Content-Language: en
Transfer-Encoding: chunked
Last-Modified: Thu, 11 Dec 2008 15:12:41 GMTLast-Modified: Thu, 11 Dec 2008 15:12:41 GMT
ETag: "aff45de9a25bc91:b439"ETag: "aff45de9a25bc91:b439"
Server: Microsoft-IIS/6.0Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NETX-Powered-By: ASP.NET
Date: Thu, 11 Dec 2008 20:38:14 GMTDate: Thu, 11 Dec 2008 20:39:18 GMT
Cache-Control: private
5 Replies
hoolioCirrostratus
Hi there,
Are you modifying the response content on LTM? If not, why did you need to enable rechunking? Can you post the full request and response headers for a request through LTM and a request direct to one of the pool members?
Also, were there really two Content-Type, Last-Modified, E-Tag, X-Powered-By and Date headers in the response(s)?
Thanks,
Aaron
Gerardo_Garcia_On LTM I have rechunking becuase we have are adding SSL for external users only but the profile implements the rechunking for every call.
I hope the following explains a little bit better the situation.
Direct Call
HTTP/1.1 206 Partial Content
Content-Type: application/octet-stream
Content-Length: 579972
Content-Range: bytes 0-579971/579972
Accept-Ranges: bytes
Last-Modified: Thu, 11 Dec 2008 15:12:41 GMT
ETag: "aff45de9a25bc91:b439"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 11 Dec 2008 20:38:14 GMT
LTM Call
HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Language: en
Transfer-Encoding: chunked
Last-Modified: Thu, 11 Dec 2008 15:12:41 GMT
ETag: "aff45de9a25bc91:b439"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 11 Dec 2008 20:39:18 GMT
X-AspNet-Version: 1.1.4322
Cache-Control: private- hoolioI don't think you'd need to enable rechunking for doing SSL decryption on LTM. Did you see issues with it disabled?
Aaron - Gerardo_Garcia_We are using rechunking because when we added the https to the payload using the STREAM expression pieces of the page were missing at the bottom of the page.
Basically, the number of letters (s) added to the page that was the number of characters missing on the browser window using the view source option. - hoolioIf you enable rechunking on the HTTP profile, LTM will use chunked encoding for every response. Deb described this in an article (Click here). I'm not sure what problem that would cause with the client or app for your application. Maybe you could open a case with F5 Support to get help in troubleshooting this.
Aaron
