Forum Discussion
Theo_12742
Apr 26, 2016Cirrus
It has to do with the way files are chunked when downloaded, and most web-based applications don't really account for this in the standard manner.
Workaround: In the HTTP profile for that virtual server, change
Response Chunking
to Rechunk
and try again.- Apr 26, 2016Thank you for the quick response, Theo! Unfortunately I'm still getting the same error message. Now I'm also getting a mixture of "page cannot be displayed" on some of the other links. If it makes a difference, the web page is built on top of a CMS - a Content Management System developed by a group called Passageways. I've asked them for assistance, but they claim not to provide load balancer support. Thus, I'm hoping to shoehorn the BIG-IP in there anyways just to see if I can. Any other areas I can look? Thanks! Steve
- Theo_12742Apr 27, 2016CirrusI think the next step is two-fold. 1) Set the logging level to debug and watch for any related messages to that VIP. The most common is a RFC2616 error, which is where the HTTP is non-standard and rejected by the F5. 2) Use a program like Fiddler or HttpWatch to monitor the client session and capture the headers regarding the link generated by the PDF and the call to the PDF itself--see if it's experiencing unexpected behavior (like calling the name of the server directly).