In our environment, the Vaadin application runs with on an embedded Jetty container behind an apache2+mod_proxy reverse proxy. Right now, even though the application itself works pretty well with browsers using HTTP 1.1, it seems to completely break for a load of users when running while the apache2 is set to be an HTTP 1.1 proxy. In those situations the upload dialog will stop at 100% (and not automatically disappear) and then the application will not see any uploaded files.
I am aware it's a bit tough to describe. Any ideas on what information I could provide to help track this down?
In our environment, the Vaadin application runs with on an embedded Jetty container behind an apache2+mod_proxy reverse proxy. Right now, even though the application itself works pretty well with browsers using HTTP 1.1, it seems to completely break for a load of users when running while the apache2 is set to be an HTTP 1.1 proxy. In those situations the upload dialog will stop at 100% (and not automatically disappear) and then the application will not see any uploaded files.
I am aware it's a bit tough to describe. Any ideas on what information I could provide to help track this down?