Forum: NGINX Strange hex numbers on my page

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
2974d09ac2541e892966b762aad84943?d=identicon&s=25 marcintom (Guest)
on 2009-04-23 14:37
(Received via mailing list)
Hi all,
I work on 0.5.26 version and yesterday I migrate to 0.6.36 version. I
have a problem
configuration looks like as in old version and allmost everything work
fine but
in the wordpress it appear some random hex number in my pge for example
before
22056 <!--Doctype,
and the end of document( 0  0 )
and in other places.

nginx.conf
(...)
            if ($host ~ xxx\.org ) {
               break;
               proxy_pass      http://127.0.0.1:8888;
            }
(...)

This hex numbers are ofcourse visible in browser.
When I tried GET my wordpress blog without nginx
there are no any numbers so the problem in 99% is on nginx side in
my opinion.
Anybody knows what is going on and can help me ?

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,1376,1376#msg-1376
96321bb7fd6f712aa7785ce2d58388f2?d=identicon&s=25 Anton Yuzhaninov (Guest)
on 2009-04-23 15:03
(Received via mailing list)
marcintom wrote:
>                break;
>                proxy_pass      http://127.0.0.1:8888;
>             }
> (...)
>
> This hex numbers are ofcourse visible in browser.
> When I tried GET my wordpress blog without nginx
> there are no any numbers so the problem in 99% is on nginx side in
> my opinion.

Problem in wordpress side - it send HTTP/1.1 chunked reply to HTTP/1.0
request from nginx.

Workaround is to add in apache httpd.conf

SetEnv force-response-1.0 1
SetEnv downgrade-1.0 1

or

BrowserMatch ".*" downgrade-1.0 force-response-1.0
2974d09ac2541e892966b762aad84943?d=identicon&s=25 marcintom (Guest)
on 2009-04-24 08:51
(Received via mailing list)
I tried first and second solution with httpd.conf and restart apche and
problem still  exist.

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,1376,1383#msg-1383
This topic is locked and can not be replied to.