HTTP/1.1 & Proxies
Proposal: 100-Continue optional under Client control
Updated test implementation for TCN available
Digest Authentication bleat
Status 100
confidentiality and the referer field
- Re: confidentiality and the referer field
- Re: confidentiality and the referer field
- Re: confidentiality and the referer field
- Re: confidentiality and the referer field
- Re: confidentiality and the referer field
- RE: confidentiality and the referer field
- RE: confidentiality and the referer field
Assigned paths
I-D ACTION:draft-ietf-http-state-man-mec-02.txt, .ps
I-D ACTION:draft-ietf-http-state-man-mec-02.txt, .ps
I-D ACTION:draft-cohen-http-305-306-responses-00.txt
I-D ACTION:draft-ietf-http-negotiate-scenario-00.txt
draft-ietf-http-negotiate-scenario.00.txt
HTTP Download
new cookie I-D submitted
Web Security
More thoughts on content negotiation
Transient content negotiation
- Re: Transient content negotiation
- Re: Transient content negotiation
- Re: Transient content negotiation
- Re: Transient content negotiation
I-D ACTION:draft-ietf-http-negotiate-scenario-00.txt
First draft of negotiation requirements document
- Re: First draft of negotiation requirements document
- Re: First draft of negotiation requirements document
- Re: First draft of negotiation requirements document
- Re: First draft of negotiation requirements document
Proposal: Vary on Cookies
- Re: Proposal: Vary on Cookies
- Re: Proposal: Vary on Cookies
- Re: Proposal: Vary on Cookies
- Re: Proposal: Vary on Cookies
Is Your Web Site A Secret?
Buggy TCP implementations. Was: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Proxy Keep-Alive
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
- Re: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
- RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- Re: ISSUE: MUST a client wait for 100 when doing PUT or POST
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Web Site Visibility
Question
cache-busting document
OPTIONS method
305/306 response codes
- RE: 305/306 response codes
- Re: 305/306 response codes
- RE: 305/306 response codes
- Re: 305/306 response codes
- Re: 305/306 response codes
- Re: 305/306 response codes
Graham Klyne on content negotiation
draft-mutz-http-attributes-02.txt
draft-ietf-http-negotiation-02.txt
Persistent connections, and 1.0 browsers
HTTP/1.1 -- who disconnects the session?
RANGE-ERROR issue: proposed resolution
Date/time on the Internet
RE: NS, Verisign, Firefly proposal [was Re: Revised charter ,milestones
Q: protocolls and fault tolerance
RE: An experiment in producing RFC1122-style requirements checkli st
Common Gateway Interface
- Re: Common Gateway Interface
- Re: Common Gateway Interface
- Re: Common Gateway Interface
- Re: Common Gateway Interface
An experiment in producing RFC1122-style requirements checklist
- Re: An experiment in producing RFC1122-style requirements checklist
- Re: An experiment in producing RFC1122-style requirements checklist
- Re: An experiment in producing RFC1122-style requirements checklist
- Re: An experiment in producing RFC1122-style requirements checklist
OPS specification
Cookie domain
Cookie domain
Cookie domain
HTTP 1.1 Issue: 403VS404
I-D ACTION:draft-ietf-http-negotiation-02.txt
URI -> URL when talking about 'moved ...'
New content negotiation draft: draft-ietf-http-negotiation-02.txt
notes from previous Editing Group meeting: goals, docking
- Re: notes from previous Editing Group meeting: goals, docking
- Revised charter milestones
- Re: Revised charter milestones
- Re: Revised charter milestones
- Re: Revised charter milestones
- Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
- Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
- Re: NS, Verisign, Firefly proposal [was Re: Revised charter ,
- Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
- Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
- Re: NS, Verisign, Firefly proposal [was Re: Revised charter ,
- Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
- Re: Revised charter milestones
- Re: Revised charter milestones
- Re: Revised charter milestones
- Revised charter milestones
HTTP Issues LAST CALL; HTTP editing group
- COMMENT: LAST CALL comment
HTTP 1.1 Issue: When To Close Connections
DES attack, help crack bad encryption!
PEP Integration in RTSP
- Re: PEP Integration in RTSP
- Re: PEP Integration in RTSP
- Re: PEP Integration in RTSP
- RE: PEP Integration in RTSP
- RE: PEP Integration in RTSP
- RE: PEP Integration in RTSP
- RE: PEP Integration in RTSP
- RE: PEP Integration in RTSP
- RE: PEP Integration in RTSP
FREE LISTING in Worldwide Directory
WEB->FAX
Announcement: A new Wiley book on World Wide Web Security
I-D ACTION:draft-ietf-http-jaye-trust-state-00.txt
draft-daviel-metadata-link-00.txt
Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Re: Rewrite of feature tag syntax rules
- Call for comments on feature tag syntax
references to obsolete RFC1522
Document Action: Use and interpretation of HTTP version numbers to Informational
RANGES (Might be nice to allow 206 response to range request without knowing total content length)
Issue: 304-LAST-MODIFIED (Should 304 include Last Modified?)
Issue: BYTE-RANGE (Is the right meta-data returned on range requests?)
request for input of managing WWW-servers.
Re: NUDGE: Our piece on Host: and URLs (Fwd)
- Re: NUDGE: Our piece on Host: and URLs (Fwd)
- Re: NUDGE: Our piece on Host: and URLs (Fwd)
Issue: BYTE-RANGE -- resolved?
"versions" -> Informational RFC
feature negotiation syntax
from the AD: content-length is invalid within multipart
RE: Indexing non-HTML objects
New feature negotiation syntax
- Re: New feature negotiation syntax
- RE: New feature negotiation syntax
- RE: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
- Re: New feature negotiation syntax
I-D ACTION:draft-ietf-http-state-man-mec-01.txt, .ps
draft-ietf-http-state-man-mec-01 submitted
Comment on PEP draft
problems with cookies
Re: IPP> Re: MIME multipart/* vs HTTP
Accept header and inline images
Slight wording error in section 13.5.4
Re: Indexing non-HTML objects
announcing: http-state mailing list
Re: IPP> MIME multipart/* vs HTTP
Re: IPP>PRO - http comments
MIME multipart/* vs HTTP
- Re: MIME multipart/* vs HTTP
- RE: MIME multipart/* vs HTTP
- Re: MIME multipart/* vs HTTP
- RE: MIME multipart/* vs HTTP
- Re: MIME multipart/* vs HTTP
Comments on PEP draft
State management
I-D ACTION:draft-ietf-http-pep-03.txt
proxy autoconfiguration
New PEP draft available as ID!
- RE: New PEP draft available as ID!
- Re: New PEP draft available as ID!
- RE: New PEP draft available as ID!
HTTP State Management Mechanism (Rev1): EndSession attribute
- Re: HTTP State Management Mechanism (Rev1): EndSession attribute
- RE: HTTP State Management Mechanism (Rev1): EndSession attribute
- RE: HTTP State Management Mechanism (Rev1): EndSession attribute
- RE: HTTP State Management Mechanism (Rev1): EndSession attribute
- Re: HTTP State Management Mechanism (Rev1): EndSession attribute
- Re: HTTP State Management Mechanism (Rev1): EndSession attribute
- Re: HTTP State Management Mechanism (Rev1): EndSession attribute
A linguistic note on unverifiable transactions
Origin Servers without Clocks
Re: Pipelining and compression effect on HTTP/1.1 proxies
- Re: Pipelining and compression effect on HTTP/1.1 proxies
- Re: Pipelining and compression effect on HTTP/1.1 proxies
- Re: Pipelining and compression effect on HTTP/1.1 proxies
- RE: Pipelining and compression effect on HTTP/1.1 proxies
- Re: Pipelining and compression effect on HTTP/1.1 proxies
Issues-list item "DISPOSITION"
- Re: Issues-list item "DISPOSITION"
- Re: Issues-list item "DISPOSITION"
- Re: Issues-list item "DISPOSITION"
Issues-list item "QZERO"
Issues-list item "LWS-DELIMITER"
"last call": draft-ietf-http-versions-01.txt
no one supports Digest
Memphis followup
Issues-list item "CACHING-CGI"
- Issues-list item "CACHING-CGI"
Issues-list item "CACHING-CGI"
- Re: Issues-list item "CACHING-CGI"
- Re: Issues-list item "CACHING-CGI"
- Re: Issues-list item "CACHING-CGI"
- Re: Issues-list item "CACHING-CGI"
Insisting on a message digest (rfc2069)
Digest Authentication, Netscape, and Microsoft
- Re: Digest Authentication, Netscape, and Microsoft
New Proposed Chunked Rules
SSL tunneling status
mid-course errors
- Re: mid-course errors
- RE: mid-course errors
- RE: mid-course errors
- Re: mid-course errors
- RE: mid-course errors
- Re: mid-course errors
HTTP practice and Year-2000: the bad(?) news
RE: chunked enc. (Was: Re: draft minutes, HTTP-WG meetings April 7)
HTTP/1.1 Pipelining
Change to Chunk Length Syntax
draft minutes, HTTP-WG meetings April 7
- chunked enc. (Was: Re: draft minutes, HTTP-WG meetings April 7)
- Re: draft minutes, HTTP-WG meetings April 7
- WARNINGS issue (was Re: draft minutes, HTTP-WG meetings April 7)
Summary, HTTP-WG meeting in Memphis
HTTP/1.1 - Retry-after for 3xx as well as 503?
1xx Clarification
- Re: 1xx Clarification
- Re: 1xx Clarification
- RE: 1xx Clarification
- RE: 1xx Clarification
- RE: 1xx Clarification
- RE: 1xx Clarification
- RE: 1xx Clarification
- RE: 1xx Clarification
- Re: 1xx Clarification
- Re: 1xx Clarification
- Re: 1xx Clarification
HTTP/1.1-TCP interactions (was Re: HTTP Connection Management(draft-ietf-http-connection-00.txt))
RE: ID: Proxy autoconfig
Can I add a link to your site from mine?
Request for HTML Draft to support Multi Direction languages.
- Re: Request for HTML Draft to support Multi Direction languages.
- Re: Request for HTML Draft to support Multi Direction languages.
RE: e-mail
Updated Issues list...
Administrivia: running on automatic
Proposed amendment to RFC2109
- FW: Proposed amendment to RFC2109
- Re: Proposed amendment to RFC2109
- Re: FW: Proposed amendment to RFC2109