Re: [apps-discuss] I-D Action: draft-nottingham-http-browser-hints-02.txt

[Mykyta Yevstifeyev <[e-mail]>]

30.08.2011 4:03, Mark Nottingham wrote:
> I didn't go in this direction because it *seems* to conflict with the STS effort in websec. Maybe someone from over there could comment?

I understand that HSTS is only useful when site declares that HTTPS must 
be used any time when connecting to it.  Specific areas/resources may 
not be declared to be so (If I'm wrong, correct me).

Anyway, an alternative is never a bad thing.

Mykyta Yevstifeyev

>
> Cheers,
>
> s
> On 30/08/2011, at 1:33 AM, Mykyta Yevstifeyev wrote:
>
>> Proposal for a new hint:
>>
>>> 5.8.  https
>>>
>>>     o  Browser Hint Name: https
>>>     o  Description: When true, this hint indicates the user agent may
>>>        use HTTPS and, correspondigly, 'https' URI scheme [RFC2818] with
>>>        the specific areas (resources) of the site.
>>>     o  Value Type: prefixlist
>>>     o  Contact: /somebody/
>> Mykyta Yevstifeyev
>>
>> 31.05.2011 9:28, Mark Nottingham wrote:
>>> FYI. Diffs at:
>>>    http://tools.ietf.org/rfcdiff?url2=draft-nottingham-http-browser-hints-02
>>>
>>> Changelog:
>>>    - removed Ref header and rearranged referer-based hints
>>>    - added 'prefixlist' value type
>>>    - changed omit-cookies from list of cookie names to prefixlist
>>>    - added caching advice for 404s
>>>
>>> Feedback appreciated, as always.
>>>
>>>
>>>
>>> Begin forwarded message:
>>>
>>>> From: [e-mail]
>>>> Date: 31 May 2011 4:22:29 PM AEST
>>>> To: [e-mail]
>>>> Subject: I-D Action: draft-nottingham-http-browser-hints-02.txt
>>>> Reply-To: [e-mail]
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>>
>>>> 	Title           : HTTP Browser Hints
>>>> 	Author(s)       : Mark Nottingham
>>>> 	Filename        : draft-nottingham-http-browser-hints-02.txt
>>>> 	Pages           : 9
>>>> 	Date            : 2011-05-30
>>>>
>>>>    Over time, Web browsers have adapted how they use HTTP based upon
>>>>    common server configurations and behaviours.  While this is necessary
>>>>    in the common case, it can be detrimental for performance and
>>>>    interoperability.
>>>>
>>>>    This document establishes a mechanism whereby origin servers can make
>>>>    available hints for browsers about their preferences and
>>>>    capabilities, without imposing overhead on their interactions or
>>>>    requiring support for them.
>>>>
>>>>    This is intended to allow browsers to safely optimise connections to
>>>>    servers.
>>>>
>>>>
>>>> A URL for this Internet-Draft is:
>>>> http://www.ietf.org/internet-drafts/draft-nottingham-http-browser-hints-02.txt
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> This Internet-Draft can be retrieved at:
>>>> ftp://ftp.ietf.org/internet-drafts/draft-nottingham-http-browser-hints-02.txt
>>>> _______________________________________________
>>>> I-D-Announce mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>> --
>>> Mark Nottingham   http://www.mnot.net/
>>>
>>>
>>>
>>> _______________________________________________
>>> apps-discuss mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>
>> _______________________________________________
>> apps-discuss mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/apps-discuss
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>