400 bad requests now returning http headers? ( crossdomain.xml )
mdounin at mdounin.ru
Tue Jun 10 19:36:24 UTC 2014
On Tue, Jun 10, 2014 at 02:49:58PM -0400, Thaxll wrote:
> I'm using Nginx to serve a file called crossdomain.xml, that file is used by
> Flash client to allow socket crossdomain Policy. It's a trick that many
> people are using instead of having a dedicated app to server that file. The
> trick is to return that xml file when nginx get a bad request. Since a
> recent version ( 1.4.7+ ) it seems that a bad request replies include HTTP
> headers and therefore breaking the Flash client ( instead of returning only
> the data without headers ). Is there a way to remove those headers? Also I
> searched in the changelog and didn't find any hints about that change?
Quote from http://nginx.org/en/CHANGES, changes with nginx 1.5.5:
*) Change: now nginx assumes HTTP/1.0 by default if it is not able to
detect protocol reliably.
More information about the nginx