incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Lutterkort (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DTACLOUD-18) Missing Host header not handled
Date Fri, 18 Feb 2011 01:25:12 GMT

     [ https://issues.apache.org/jira/browse/DTACLOUD-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Lutterkort updated DTACLOUD-18:
-------------------------------------

    Description: 
According to HTTP 1.1[1], requests must have a Host header. If the header is missing, the
response should be a '400 Bad request'

Right now, we carry on and produce improper results, since URL's embedded in responses either
do not contain the port number, or have port number 0. Example:

> curl -H 'Host:' http://localhost:3001/api

<api driver='mock' version='0.2.0'>
  <link href='http://localhost:0/api/buckets' rel='buckets'>
  </link>
  ...
</api>

[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

  was:
According to HTTP 1.1[1], requests must have a Host header. If the header is missing, the
response should be a '400 Bad request'

Right now, we carry on and produce improper results, since URL's embedded in responses either
do not contain the port number, or have port number 0. Example:

> curl -H 'Host:' http://localhost:3001/api

&lt;api driver='mock' version='0.2.0'>
  &lt;link href='http://localhost:0/api/buckets' rel='buckets'>
  &lt;/link>
  ...
&lt;/api>

[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html


> Missing Host header not handled
> -------------------------------
>
>                 Key: DTACLOUD-18
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-18
>             Project: DeltaCloud
>          Issue Type: Bug
>            Reporter: David Lutterkort
>            Assignee: David Lutterkort
>            Priority: Minor
>
> According to HTTP 1.1[1], requests must have a Host header. If the header is missing,
the response should be a '400 Bad request'
> Right now, we carry on and produce improper results, since URL's embedded in responses
either do not contain the port number, or have port number 0. Example:
> > curl -H 'Host:' http://localhost:3001/api
> <api driver='mock' version='0.2.0'>
>   <link href='http://localhost:0/api/buckets' rel='buckets'>
>   </link>
>   ...
> </api>
> [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message