Re: draft-ieft-http-options-00.txt

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Jeffrey Mogul: "Re: draft-ieft-http-options-00.txt"
• Previous message: Jeffrey Mogul: "Re: Comments on OPTIONS draft"
• In reply to: Dave Kristol: "draft-ieft-http-options-00.txt"
• Next in thread: Jeffrey Mogul: "Re: draft-ieft-http-options-00.txt"

    I read through the I-D, thinking about how an origin server that
    supports cookies (i.e., RFC 2109) might respond to
    
	    OPTIONS * HTTP/1.1
	    Compliance: rfc=2109
    
    The problem is that (I believe) most of the support is not in the
    server itself, but in CGIs.  Consequently, the server software may not
    be able to answer authoritatively about whether RFC 2109 is supported,
    because that may depend on what each individual CGI does.
    
    What advice would the authors (or others) give?
    

• Next message: Jeffrey Mogul: "Re: draft-ieft-http-options-00.txt"
• Previous message: Jeffrey Mogul: "Re: Comments on OPTIONS draft"
• In reply to: Dave Kristol: "draft-ieft-http-options-00.txt"
• Next in thread: Jeffrey Mogul: "Re: draft-ieft-http-options-00.txt"