You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/11/17 04:30:28 UTC

[jira] Created: (TS-540) HTTPS to origin stalls with chunked responses

HTTPS to origin stalls with chunked responses
---------------------------------------------

                 Key: TS-540
                 URL: https://issues.apache.org/jira/browse/TS-540
             Project: Traffic Server
          Issue Type: Bug
          Components: SSL
    Affects Versions: 2.1.4
            Reporter: Leif Hedstrom
            Priority: Critical
             Fix For: 2.1.5


With a remap rule like this


map http://loki.ogre.com/ogre  https://www.ogre.com


A request for a "static" object, which responds with Content-Length: header, works fine, e.g. fetch

http://loki.ogre.com/ogre/files/bluebreeze_logo.png


Fetching an object which is served chunked encode will stall the request, and serve only a partial response, e.g. fetch

http://loki.ogre.com/ogre


Changing the remap rule to proxy to http:// makes both cases work fine.

This bug was originally mentioned to my by Charlie G.

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


[jira] Assigned: (TS-540) HTTPS to origin stalls with chunked responses

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

Leif Hedstrom reassigned TS-540:
--------------------------------

    Assignee: Leif Hedstrom

> HTTPS to origin stalls with chunked responses
> ---------------------------------------------
>
>                 Key: TS-540
>                 URL: https://issues.apache.org/jira/browse/TS-540
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: SSL
>    Affects Versions: 2.1.4
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>            Priority: Critical
>             Fix For: 2.1.5
>
>
> With a remap rule like this
> map http://loki.ogre.com/ogre  https://www.ogre.com
> A request for a "static" object, which responds with Content-Length: header, works fine, e.g. fetch
> http://loki.ogre.com/ogre/files/bluebreeze_logo.png
> Fetching an object which is served chunked encode will stall the request, and serve only a partial response, e.g. fetch
> http://loki.ogre.com/ogre
> Changing the remap rule to proxy to http:// makes both cases work fine.
> This bug was originally mentioned to my by Charlie G.

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


[jira] Resolved: (TS-540) HTTPS to origin stalls with chunked responses

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

Leif Hedstrom resolved TS-540.
------------------------------

    Resolution: Fixed

> HTTPS to origin stalls with chunked responses
> ---------------------------------------------
>
>                 Key: TS-540
>                 URL: https://issues.apache.org/jira/browse/TS-540
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: SSL
>    Affects Versions: 2.1.4
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>            Priority: Critical
>             Fix For: 2.1.5
>
>
> With a remap rule like this
> map http://loki.ogre.com/ogre  https://www.ogre.com
> A request for a "static" object, which responds with Content-Length: header, works fine, e.g. fetch
> http://loki.ogre.com/ogre/files/bluebreeze_logo.png
> Fetching an object which is served chunked encode will stall the request, and serve only a partial response, e.g. fetch
> http://loki.ogre.com/ogre
> Changing the remap rule to proxy to http:// makes both cases work fine.
> This bug was originally mentioned to my by Charlie G.

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