I think Owen clearly gives an example of why we absolutely need to  
know the URL of the requested resource.

Multisite requires it–that's a pretty darn good reason.

Has anyone _besides_ Geoffrey actually run into this issue?

On Sep 4, 2008, at 8:16 PM, Owen Winkler wrote:

>
> Michael C. Harris wrote:
>> On Thu, Sep 04, 2008 at 08:04:46PM -0400, Owen Winkler wrote:
>>> Geoffrey Sneddon wrote:
>>>> We use HTTP_HOST to get the host for the authority of the absolute
>>>> IRI. What else can we use for the host if we do not have it?  All I
>>>> can think that we would always have is the server IP, which may  
>>>> not be
>>>> ideal if it is an internal IP. The only place we must use absolute
>>>> URIs is the location header in HTTP for redirects (everything  
>>>> supports
>>>> relative URIs for it, though). If we don't bother to use absolute  
>>>> IRIs
>>>> (or authority relative IRIs) elsewhere we never hit this issue  
>>>> apart
>>>> from in that case.
>>>>
>>> Outputting URLs is not the only place where HTTP_HOST is used.  It  
>>> is
>>> used in the Site class to find the correct config, plugin, and theme
>>> data for a site.  There may be other places it is used.
>>>
>>> I think there isn't much to discuss on this topic.  Was there an  
>>> implied
>>> question as to why we use absolute URLs?  If so, no, there's no  
>>> reason.
>>>  But as I said above, we do use the HTTP_HOST for at least one  
>>> other thing.
>>
>> Isn't the issue that it's not always available, because HTTP 1.0
>> clients don't send the Host header ?
>>
>
> Right, which is to say that the statement "If we don't bother to use
> absolute IRIs elsewhere we never hit this issue apart from in that
> case." isn't entirely true.  If the HTTP_HOST is missing, at least the
> one other thing I mentioned will fail.
>
> I'm sure there is some reason why we should support HTTP 1.0 without
> host headers, but I can't bring myself to think on it.
>
> Owen
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to