Mailing List Archive

Unwanted CRLF and numbers in pages processed by backhand
Aloha everybody:

All responses from backhand contain unwanted numbers (line lentgh in hex)
and CRLF.
As soon as backhand processes the requests on another cluster machine, the
response contains an additional CRLF in each line as well as a number
(length of line to come in hex?)
Below are some examples of the responses is receive. Maybe someone can help
me there!

---
Here is an example from the master:
---
a8
CGI/1.0 test script report:

argc is 0. argv is .

SERVER_SOFTWARE = Apache/1.3.23 (Unix) (Red-Hat/Linux) mod_ssl/2.8.7
OpenSSL/0.9.6b mod_perl/1.26 mod_backhand/1.2.1

14d
SERVER_NAME = comp5.domain.com
GATEWAY_INTERFACE = CGI/1.1
SERVER_PROTOCOL = HTTP/1.1
SERVER_PORT = 443
REQUEST_METHOD = GET
HTTP_ACCEPT = */*
PATH_INFO =
PATH_TRANSLATED =
SCRIPT_NAME = /bh/cgi-bin/test-cgi
QUERY_STRING = test=0
REMOTE_HOST =
REMOTE_ADDR = 172.16.1.41
REMOTE_USER =
AUTH_TYPE =
CONTENT_TYPE =
CONTENT_LENGTH =

0

---
Here is a response from one of the cluster servers:
---
1c
CGI/1.0 test script report:

1


15
argc is 0. argv is .

1


75
SERVER_SOFTWARE = Apache/1.3.23 (Unix) (Red-Hat/Linux) mod_ssl/2.8.7
OpenSSL/0.9.6b mod_perl/1.26 mod_backhand/1.2.1

22
SERVER_NAME = comp4.domain.com

1c
GATEWAY_INTERFACE = CGI/1.1

1b
SERVER_PROTOCOL = HTTP/1.1

12
SERVER_PORT = 443

15
REQUEST_METHOD = GET

12
HTTP_ACCEPT = */*

d
PATH_INFO =
etc.
Unwanted CRLF and numbers in pages processed by backhand [ In reply to ]
> SERVER_SOFTWARE = Apache/1.3.23 (Unix) (Red-Hat/Linux) mod_ssl/2.8.7
> OpenSSL/0.9.6b mod_perl/1.26 mod_backhand/1.2.1

First off, upgrade to mod_backhand/1.2.2 :-)

You also should upgrade to Apache 1.3.27, I _think_ there may be some
chunked encoding bugs in there.

The problem you are seeing is that mod_backhand is not proxying the a
chunked response message correctly. I believe that with the newest
version of Apache+mod_backhand, this should be resolved.

If that doesn't work, you can resort to issuing a force-downgrade like
so:

BrowserMatch "MSIE" downgrade-1.0 force-response-1.0

As chucked-encoding is an HTTP/1.1 thing, it will no longer be a
problem. Do the upgrade first as downgrading everyone's connections to
1.0 seems... rude.

--
Theo Schlossnagle
Principal Consultant
OmniTI Computer Consulting, Inc. -- http://www.omniti.com/
Phone: +1 410 872 4910 x201 Fax: +1 410 872 4911
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7