You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Vishal (JIRA)" <ji...@apache.org> on 2007/12/05 15:54:43 UTC

[jira] Created: (DIRMINA-487) Fix HTTP response with no content-length header

Fix HTTP response with no content-length header
-----------------------------------------------

                 Key: DIRMINA-487
                 URL: https://issues.apache.org/jira/browse/DIRMINA-487
             Project: MINA
          Issue Type: Bug
          Components: Protocol - HTTP, Statemachine
    Affects Versions: 2.0.0-M1
         Environment: All platforms
            Reporter: Vishal
             Fix For: 2.0.0-M1


HTTP/1.1 responses (content part) which have the content-length header missing are accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protcol filter needs to be fixed for this.

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


[jira] Closed: (DIRMINA-487) Fix HTTP response with no content-length header

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRMINA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRMINA-487.
-------------------------------------


> Fix HTTP response with no content-length header
> -----------------------------------------------
>
>                 Key: DIRMINA-487
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-487
>             Project: MINA
>          Issue Type: Bug
>          Components: Protocol - HTTP
>         Environment: All platforms
>            Reporter: Vishal
>            Assignee: Trustin Lee
>
> HTTP/1.1 responses (content part) which have the content-length header missing are not accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protocol filter needs to be fixed for this.

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


[jira] Updated: (DIRMINA-487) Fix HTTP response with no content-length header

Posted by "Vishal (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRMINA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vishal updated DIRMINA-487:
---------------------------

    Description: HTTP/1.1 responses (content part) which have the content-length header missing are not accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protocol filter needs to be fixed for this.  (was: HTTP/1.1 responses (content part) which have the content-length header missing are accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protcol filter needs to be fixed for this.)

> Fix HTTP response with no content-length header
> -----------------------------------------------
>
>                 Key: DIRMINA-487
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-487
>             Project: MINA
>          Issue Type: Bug
>          Components: Protocol - HTTP, Statemachine
>    Affects Versions: 2.0.0-M1
>         Environment: All platforms
>            Reporter: Vishal
>             Fix For: 2.0.0-M1
>
>
> HTTP/1.1 responses (content part) which have the content-length header missing are not accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protocol filter needs to be fixed for this.

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


[jira] Resolved: (DIRMINA-487) Fix HTTP response with no content-length header

Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRMINA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee resolved DIRMINA-487.
---------------------------------

    Resolution: Fixed

> Fix HTTP response with no content-length header
> -----------------------------------------------
>
>                 Key: DIRMINA-487
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-487
>             Project: MINA
>          Issue Type: Bug
>          Components: Protocol - HTTP
>         Environment: All platforms
>            Reporter: Vishal
>            Assignee: Trustin Lee
>
> HTTP/1.1 responses (content part) which have the content-length header missing are not accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protocol filter needs to be fixed for this.

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


[jira] Updated: (DIRMINA-487) Fix HTTP response with no content-length header

Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRMINA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee updated DIRMINA-487:
--------------------------------

          Component/s:     (was: Statemachine)
    Affects Version/s:     (was: 2.0.0-M1)
        Fix Version/s:     (was: 2.0.0-M1)
             Assignee: Trustin Lee

Fixed.

> Fix HTTP response with no content-length header
> -----------------------------------------------
>
>                 Key: DIRMINA-487
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-487
>             Project: MINA
>          Issue Type: Bug
>          Components: Protocol - HTTP
>         Environment: All platforms
>            Reporter: Vishal
>            Assignee: Trustin Lee
>
> HTTP/1.1 responses (content part) which have the content-length header missing are not accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protocol filter needs to be fixed for this.

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