[jira] Commented: (ASYNCWEB-12) AsyncWeb does not understand the Status-Header e.g. sent by FastCGI backends.

["Sangjin Lee (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ASYNCWEB-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593495#action_12593495 ] 

Sangjin Lee commented on ASYNCWEB-12:
-------------------------------------

Maybe I didn't fully understand how fastcgi works or what this issue is about, but strictly speaking, the aforementioned response is not a response that conforms to the HTTP RFC (2616), no?  AFAIK, an HTTP response that does not have a properly formatted status line is not a valid response...  I'm curious, do browsers (IE, Firefox, ...) understand and accept such responses?

My concern is, yes we could change the HttpResponseDecoder so that it recognizes the status header (this doesn't seem to be part of the RFC either) and recognize it as the status even if the status line is not formed, but that would deviate from the RFC, and the same class would be used in parsing responses that are coming over the wire...

Am I misunderstanding what's being requested?

> AsyncWeb does not understand the Status-Header e.g. sent by FastCGI backends.
> -----------------------------------------------------------------------------
>
>                 Key: ASYNCWEB-12
>                 URL: https://issues.apache.org/jira/browse/ASYNCWEB-12
>             Project: Asyncweb
>          Issue Type: Bug
>          Components: Common
>         Environment: AsyncWeb 0.9.0 CVS used in AsyncFCGI
>            Reporter: Daniel Wirtz
>            Priority: Trivial
>
> When a Status header is provided, AsyncWeb does not transform it into the equivalent HTTPStatus in a HttpResponse.
> A response from a FastCGI backend could look like this:
> Content-Type: text/html\r\n
> Status: 404\r\n
> \r\n
> File not found!
> or
> Content-Type: text/html\r\n
> Status: 404 Some Custom Message\r\n
> \r\n
> File not found!
> in PHP this looks like:
> header("404: Some Custom Message"); or
> header("HTTP/1.1 404 Not Found"); etc.
> -> both produce the Status-Header.
> As far as I know the webserver (this would be asyncweb in this case) converts the status header into the correct http status (e.g. "HTTP/1.1 404 Not Found"). I'm using PHP a lot, the status header is the default behaviour and Apache / Lighttpd handle it this way (even with mod_php instead of FastCGI). I don't want to preparse the response because of unneccessary double checking instead of simply feeding it into a HttpResponseDecoder. However, I think the status header is not part of the http specification but since it's used a lot, it would make sence.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.