I commented the stuff out and it works. I also submitted a bug report.
Thanks guys
Kaushal Jha wrote:
> keepchar = buffer[12];
> if (keepchar == '\0') {
> ap_log_error(APLOG_MARK, APLOG_WARNING, 0,
> r->server, "proxy: bad HTTP/%d.%d status
> line " "returned by %s (%s)", major,
> minor, r->uri, r->method);
>
> where char *buffer is the line of the server response "HTTP/#.# ###*"
> yes true , to reframe , the apache proxy logs the error when it does
> not see a space after the "200" in this case .
>
> best of luck
>
>
> ----- Original Message -----
> From: "Graham Leggett" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Friday, October 17, 2003 5:03 PM
> Subject: Re: mod_proxy warning - status line - please assist
>
>
> > Kaushal Jha, ZEDO wrote:
> >
> > > thats becoz the server above it sent a
> > >
> > > "HTTP/1.1 200" instead of "HTTP/1.1 200 OK"
> > >
> > > the after the status number 200 apache was expecting an "OK"
> > > :)
> >
> > Not strictly true - the spec says the line must read
> > "HTTP/<major>.<minor> XXX <response string>", and the response
> > string can be "". The thing is the space after the XXX and before
> > the possibly empty result string must be there.
> >
> > Apparently the space is there though according to the original
> > post, so it could be a problem with the way Apache handles empty
> > result strings.
> >
> > Regards,
> > Graham
> > --
> >
