Re: Question re. OPTIONS, ALLOW

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Paul Leach: "Re: more minor Digest Auth editorial comments"
• Previous message: Paul Leach: "Proxies and Digest Auth"
• Maybe in reply to: Ravi Shankar: "Question re. OPTIONS, ALLOW"

Roy wrote:

>  No, because Allow refers to the allowed methods of a
>  particular resource and the others refer to the
>  capabilities of the application on the server end of the
>  client's immediate connection.  Therefore, Allow is
>  independent of the means of communication (the
>  intermediaries involved), whereas OPTIONS and Public
>  refer to the capabilities of the currently communicating
>  neighbor.

I wanted to note as an aside that this is precisely the kind of issue that  
PEP 'scope' addresses. Rather than per-header table lookups that imply  
properties-about-orignal-resource, properties-about-resource-as-caches,  
properties-about-immediate-connection, and properties-about-origin-services,  
PEP scope and strength tagging allows proxies to reason exactly about  
disposing of unknown features.

See Section 3.4 and Appendix A.3 for more details:  
http://www.w3.org/pub/WWW/TR/WD-http-pep.html

Back to the debate at hand,
Rohit Khare

• Next message: Paul Leach: "Re: more minor Digest Auth editorial comments"
• Previous message: Paul Leach: "Proxies and Digest Auth"
• Maybe in reply to: Ravi Shankar: "Question re. OPTIONS, ALLOW"