I have a strange problem, and not sure what could even be wrong. I have a new setup: 2008 R2, IIS 7, AAR 2.5, urlrewrite 2. I have a primary website that accepts all the traffic on ports 80/443, performing a url rewire routing the traffic for app1.domain.com
ports 180/1443, and app2.domain.com to ports 280/2443. Setup is straight forward and is working for the most part. Except that some PDF documents are never returned when using the Chrome browser, going through the reverse-proxy over SSH. e.g. using Chrome
https://app2.domain.com/my.pdf (through reverse-proxy) will never complete https://app2.domain.com:2443/my.pdf (direct to app) works fine Using IE, or FireFox, both through the reverse-proxy and direct to app work fine. The problem seems only with Chrome,
and with only some PDF documents on my site. The only difference I can see between going directly to the app (on ports 280/2443) and going through the reverse-proxy (on ports 80/443) is that the document is split up going through the reverse-proxy. By this
I mean in the IIS log I see several responses 200 followed by several 206 messages. Is there a way to force IIS to return the PDF as a single document? Does anyone know any issues with Chrome and ARR, urlrewrite? Does anyone have any ideas as to what is causing
this strange problem? Any help appreciated
↧