ietf-http-wg@w3.org from April to June 1997 by author

Act Now For Your

• FREE LISTING in Worldwide Directory (Friday, 16 May)

Adam M. Costello

• webmaster@website (Tuesday, 1 April)

Adam Wierzbicki

• Re: Ignore proxy (Wednesday, 2 April)
• Ignore proxy (Wednesday, 2 April)

Albert Lunde

• Re: An experiment in producing RFC1122-style requirements checklist (Monday, 2 June)
• Re: Rewrite of feature tag syntax rules (Friday, 16 May)
• Re: webmaster@website (Tuesday, 1 April)

Alessandro Monteiro Lima

• Web Security (Thursday, 19 June)

Anawat Chankhunthod

• Re: Proxy Keep-Alive (Wednesday, 11 June)

Andreas Brusinsky

• Re: Q: protocolls and fault tolerance (Friday, 30 May)
• Q: protocolls and fault tolerance (Friday, 30 May)

Andrew Daviel

• Re: cache-busting document (Wednesday, 11 June)
• Re: cache-busting document (Tuesday, 10 June)
• draft-daviel-metadata-link-00.txt (Thursday, 15 May)
• Re: Indexing non-HTML objects (Wednesday, 7 May)
• Re: Indexing non-HTML objects (Tuesday, 6 May)
• Re: Indexing non-HTML objects (Saturday, 3 May)
• Accept header and inline images (Saturday, 3 May)
• Re: Indexing non-HTML objects (Saturday, 3 May)
• Re: Issues-list item "CACHING-CGI" (Thursday, 17 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: HTTP practice and Year-2000: the bad(?) news (Wednesday, 16 April)

Andrew Goodman

• Proxy Keep-Alive (Wednesday, 11 June)

Andy Norman

• Administrivia: running on automatic (Friday, 4 April)

Anonymous

• DES attack, help crack bad encryption! (Tuesday, 20 May)

Anselm Baird_Smith

• RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests? (Wednesday, 11 June)

Ari Luotonen

• Re: HTTP practice and Year-2000: the bad(?) news (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Digest Authentication, Netscape, and Microsoft (Tuesday, 15 April)

Avi Rubin

• Announcement: A new Wiley book on World Wide Web Security (Thursday, 15 May)

Ben Laurie

• Re: Question (Wednesday, 11 June)
• Re: cache-busting document (Saturday, 7 June)
• Re: An experiment in producing RFC1122-style requirements checklist (Thursday, 29 May)
• Re: MIME multipart/* vs HTTP (Tuesday, 6 May)
• Re: webmaster@website (Tuesday, 1 April)

Benjamin Franz

• Re: Revised charter milestones (Wednesday, 28 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Monday, 12 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Saturday, 10 May)
• Re: Indexing non-HTML objects (Friday, 2 May)
• Back from the grave: Unverifiable Transactions and Cookies (Thursday, 24 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Wednesday, 23 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Wednesday, 23 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)

Bob Briscoe

• HTTP/1.1 - Retry-after for 3xx as well as 503? (Thursday, 10 April)
• HTTP/1.1-TCP interactions (was Re: HTTP Connection Management(draft-ietf-http-connection-00.txt)) (Monday, 7 April)

Bob Denny

• Re: mid-course errors (Monday, 14 April)

Bob Monsour

• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)

carl f GRIFFITH

• Re: Comment on PEP draft (Wednesday, 28 May)
• Cookie domain (Wednesday, 28 May)
• Cookie domain (Wednesday, 28 May)
• Re: DES attack, help crack bad encryption! (Thursday, 22 May)

Carlos A. Varela

• Re: Common Gateway Interface (Thursday, 29 May)

Craig Tice

• RE: Indexing non-HTML objects (Tuesday, 6 May)

Dan Connolly

• Re: privacy platforms (Thursday, 17 April)

Daniel DuBois

• Re: HTTP State Management Mechanism (Rev1): EndSession attribute (Thursday, 1 May)
• Re: Digest Authentication, Netscape, and Microsoft (Tuesday, 15 April)

Daniel LaLiberte

• Feature negotiation requirements (Tuesday, 10 June)
• Issues-list item "CACHING-CGI" (Wednesday, 16 April)

Dave Kristol

• Digest Authentication bleat (Thursday, 26 June)
• new cookie I-D submitted (Thursday, 19 June)
• Re: New feature negotiation syntax (Thursday, 5 June)
• Re: HTTP 1.1 Issue: When To Close Connections (Friday, 23 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Saturday, 10 May)
• Issue: BYTE-RANGE -- resolved? (Friday, 9 May)
• draft-ietf-http-state-man-mec-01 submitted (Monday, 5 May)
• announcing: http-state mailing list (Thursday, 1 May)
• Re: MIME multipart/* vs HTTP (Wednesday, 30 April)
• Re: State management (Tuesday, 29 April)
• no one supports Digest (Thursday, 17 April)
• RE: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: mid-course errors (Wednesday, 16 April)
• Re: mid-course errors (Tuesday, 15 April)
• RE: mid-course errors (Tuesday, 15 April)
• Digest Authentication, Netscape, and Microsoft (Monday, 14 April)
• SSL tunneling status (Monday, 14 April)
• mid-course errors (Monday, 14 April)
• chunked enc. (Was: Re: draft minutes, HTTP-WG meetings April 7) (Friday, 11 April)

David W. Morris

• Proposal: 100-Continue optional under Client control (Monday, 30 June)
• Re: Status 100 (Friday, 27 June)
• Re: confidentiality and the referer field (Thursday, 26 June)
• Re: Assigned paths (Thursday, 26 June)
• Re: OPTIONS method (Sunday, 15 June)
• Re: Proposal: Vary on Cookies (Friday, 13 June)
• Re: Proposal: Vary on Cookies (Thursday, 12 June)
• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Wednesday, 11 June)
• Re: MUST a client wait for 100 when doing PUT or POST? (Wednesday, 11 June)
• RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests? (Wednesday, 11 June)
• RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests? (Wednesday, 11 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Wednesday, 11 June)
• Re: New feature negotiation syntax (Tuesday, 10 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: cache-busting document (Tuesday, 10 June)
• Re: cache-busting document (Sunday, 8 June)
• Re: cache-busting document (Sunday, 8 June)
• Re: HTTP/1.1 -- who disconnects the session? (Friday, 6 June)
• Re: COMMENT: LAST CALL comment (Wednesday, 4 June)
• Re: COMMENT: LAST CALL comment (Wednesday, 4 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• Re: An experiment in producing RFC1122-style requirements checklist (Tuesday, 3 June)
• Re: Common Gateway Interface (Friday, 30 May)
• Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones (Wednesday, 28 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: feature negotiation syntax (Tuesday, 13 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Saturday, 10 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Saturday, 10 May)
• Re: Indexing non-HTML objects (Tuesday, 6 May)
• Re: Indexing non-HTML objects (Saturday, 3 May)
• Re: Indexing non-HTML objects (Saturday, 3 May)
• Re: HTTP State Management Mechanism (Rev1): EndSession attribute (Thursday, 1 May)
• Re: State management (Tuesday, 29 April)
• Re: A linguistic note on unverifiable transactions (Friday, 25 April)
• Re: A linguistic note on unverifiable transactions (Thursday, 24 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)
• Re: mid-course errors (Saturday, 19 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: mid-course errors (Tuesday, 15 April)
• Re: Digest Authentication, Netscape, and Microsoft (Tuesday, 15 April)
• Re: ID: Proxy autoconfig (Friday, 11 April)
• Re: HTTP/1.1 Pipelining (Friday, 11 April)
• Re: chunked enc. (Was: Re: draft minutes, HTTP-WG meetings April 7) (Friday, 11 April)
• RE: ID: Proxy autoconfig (Thursday, 10 April)

Donald Neal

• Re: Pipelining and compression effect on HTTP/1.1 proxies (Wednesday, 23 April)

Doug Crow

• RE: 1xx Clarification (Tuesday, 15 April)

Drazen Kacar

• Re: cache-busting document (Wednesday, 11 June)
• Re: cache-busting document (Sunday, 8 June)
• Re: cache-busting document (Sunday, 8 June)
• Re: cache-busting document (Saturday, 7 June)
• Re: 305/306 response codes (Saturday, 7 June)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)

Dylan Barrell

• Re: Common Gateway Interface (Friday, 30 May)
• Re: Common Gateway Interface (Friday, 30 May)
• Common Gateway Interface (Thursday, 29 May)

Erez Levin

• Request for HTML Draft to support Multi Direction languages. (Sunday, 6 April)

Eric Harley

• Re: WEB->FAX (Friday, 16 May)
• Re: WEB->FAX (Friday, 16 May)
• Re: Can I add a link to your site from mine? (Sunday, 6 April)

Fisher Mark

• RE: Digest Authentication bleat (Monday, 30 June)
• RE: Digest Authentication, Netscape, and Microsoft (Thursday, 17 April)
• RE: Issues-list item "CACHING-CGI" (Thursday, 17 April)

Foteos Macrides

• Re: ftp URL stuff (was MIME multipart/* vs HTTP) (Tuesday, 6 May)
• Re: FTP urls (Tuesday, 6 May)

Fred Douglis

• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)

George Carrette

• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)

Graham Klyne

• Re: Assigned paths (Friday, 27 June)
• draft-ietf-http-negotiate-scenario.00.txt (Monday, 23 June)
• Re: Transient content negotiation (Sunday, 22 June)
• Re: Transient content negotiation (Sunday, 22 June)
• More thoughts on content negotiation (Wednesday, 18 June)
• Transient content negotiation (Wednesday, 18 June)
• draft-mutz-http-attributes-02.txt (Friday, 6 June)
• draft-ietf-http-negotiation-02.txt (Friday, 6 June)

Gregory J. Woodhouse

• Re: Indexing non-HTML objects (Saturday, 3 May)
• proxy autoconfiguration (Monday, 28 April)
• backoff (Re: 1xx Clarification) (Monday, 21 April)
• Re: no one supports Digest (Thursday, 17 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: mid-course errors (Monday, 14 April)
• Re: webmaster@website (Tuesday, 1 April)
• Re: webmaster@website (Tuesday, 1 April)

guthery@austin.sar.slb.com

• Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones (Thursday, 29 May)

Hallam-Baker

• Re: Assigned paths (Monday, 30 June)
• Re: confidentiality and the referer field (Friday, 27 June)
• Re: confidentiality and the referer field (Thursday, 26 June)
• Re: confidentiality and the referer field (Thursday, 26 June)
• confidentiality and the referer field (Thursday, 26 June)
• Re: NS, Verisign, Firefly proposal [was Re: Revised charter ,milestones (Friday, 30 May)
• Re: Common Gateway Interface (Friday, 30 May)
• Re: Common Gateway Interface (Thursday, 29 May)
• Re: NS, Verisign, Firefly proposal [was Re: Revised charter , (Thursday, 29 May)
• Re: MIME multipart/* vs HTTP (Tuesday, 6 May)
• Re: New PEP draft available as ID! (Wednesday, 30 April)
• Re: MIME multipart/* vs HTTP (Wednesday, 30 April)
• Re: MIME multipart/* vs HTTP (Wednesday, 30 April)
• Re: Digest Authentication, Netscape, and Microsoft (Tuesday, 15 April)

Harald.T.Alvestrand@uninett.no

• Re: DES attack, help crack bad encryption! (Thursday, 22 May)

Harrie Hazewinkel

• request for input of managing WWW-servers. (Monday, 12 May)

Henning Schulzrinne

• Re: PEP Integration in RTSP (Saturday, 17 May)

Henrik Frystyk Nielsen

• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Wednesday, 11 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: Comment on PEP draft (Monday, 19 May)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: PEP Integration in RTSP (Monday, 19 May)
• Re: feature negotiation syntax (Tuesday, 13 May)
• RANGES (Might be nice to allow 206 response to range request without knowing total content length) (Monday, 12 May)
• Issue: 304-LAST-MODIFIED (Should 304 include Last Modified?) (Monday, 12 May)
• Issue: BYTE-RANGE (Is the right meta-data returned on range requests?) (Monday, 12 May)
• Re: Issue: BYTE-RANGE -- resolved? (Monday, 12 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Monday, 12 May)
• Re: Comment on PEP draft (Thursday, 8 May)
• Slight wording error in section 13.5.4 (Friday, 2 May)
• Re: New PEP draft available as ID! (Thursday, 1 May)
• RE: New PEP draft available as ID! (Thursday, 1 May)
• Re: Comments on PEP draft (Thursday, 1 May)
• New PEP draft available as ID! (Monday, 28 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Wednesday, 23 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)

Henry Sanders (Exchange)

• RE: Pipelining and compression effect on HTTP/1.1 proxies (Wednesday, 23 April)
• RE: mid-course errors (Tuesday, 15 April)
• RE: chunked enc. (Was: Re: draft minutes, HTTP-WG meetings April 7) (Friday, 11 April)

http-wg@cuckoo.hpl.hp.com

• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)

Internet-Drafts@ietf.org

• I-D ACTION:draft-ietf-http-state-man-mec-02.txt, .ps (Tuesday, 24 June)
• I-D ACTION:draft-ietf-http-state-man-mec-02.txt, .ps (Tuesday, 24 June)
• I-D ACTION:draft-cohen-http-305-306-responses-00.txt (Monday, 23 June)
• I-D ACTION:draft-ietf-http-negotiate-scenario-00.txt (Monday, 23 June)
• I-D ACTION:draft-ietf-http-negotiate-scenario-00.txt (Tuesday, 17 June)
• I-D ACTION:draft-ietf-http-negotiation-02.txt (Wednesday, 28 May)
• I-D ACTION:draft-ietf-http-jaye-trust-state-00.txt (Thursday, 15 May)
• I-D ACTION:draft-ietf-http-state-man-mec-01.txt, .ps (Tuesday, 6 May)
• I-D ACTION:draft-ietf-http-pep-03.txt (Tuesday, 29 April)

Iole Pansino

• Cookie domain (Wednesday, 28 May)
• problems with cookies (Monday, 5 May)

Jaye, Dan

• RE: NS, Verisign, Firefly proposal [was Re: Revised charter ,milestones (Friday, 30 May)
• FW: Proposed amendment to RFC2109 (Friday, 4 April)
• Proposed amendment to RFC2109 (Friday, 4 April)

Jeff de la Beaujardiere

• Re: Assigned paths (Monday, 30 June)
• references to obsolete RFC1522 (Wednesday, 14 May)

Jeffrey Mogul

• Re: 305/306 response codes (Wednesday, 11 June)
• Re: Question (Wednesday, 11 June)
• RANGE-ERROR issue: proposed resolution (Thursday, 5 June)
• An experiment in producing RFC1122-style requirements checklist (Thursday, 29 May)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Friday, 25 April)
• WARNINGS issue (was Re: draft minutes, HTTP-WG meetings April 7) (Tuesday, 22 April)
• Re: 1xx Clarification (Monday, 21 April)
• Re: 1xx Clarification (Friday, 18 April)
• Re: mid-course errors (Friday, 18 April)
• Re: Issues-list item "CACHING-CGI" (Thursday, 17 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Issues-list item "CACHING-CGI" (Tuesday, 15 April)
• Re: mid-course errors (Tuesday, 15 April)
• Re: mid-course errors (Tuesday, 15 April)
• Re: mid-course errors (Tuesday, 15 April)
• Re: HTTP/1.1 Pipelining (Monday, 14 April)
• Re: HTTP/1.1 Pipelining (Monday, 14 April)
• Re: HTTP practice and Year-2000: the bad(?) news (Monday, 14 April)
• HTTP practice and Year-2000: the bad(?) news (Friday, 11 April)

Jim Gettys

• Buggy TCP implementations. Was: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Wednesday, 11 June)
• Re: New feature negotiation syntax (Tuesday, 10 June)
• RE: 1xx Clarification (Thursday, 17 April)
• RE: ID: Proxy autoconfig (Tuesday, 8 April)
• RE: ID: Proxy autoconfig (Tuesday, 8 April)
• Updated Issues list... (Friday, 4 April)
• Re: Process for closing out issues list (Wednesday, 2 April)

Jim Whitehead

• Re: draft-daviel-metadata-link-00.txt (Thursday, 15 May)
• Re: Indexing non-HTML objects (Wednesday, 7 May)
• Comments on PEP draft (Wednesday, 30 April)

Joanne Stevens

• Can I add a link to your site from mine? (Saturday, 5 April)

Joel N. Weber II

• Re: New feature negotiation syntax (Wednesday, 4 June)

John C. Mallery

• Re: Common Gateway Interface (Thursday, 29 May)
• HTTP 1.1 Issue: When To Close Connections (Friday, 23 May)
• Re: Change to Chunk Length Syntax (Sunday, 13 April)

John Franks

• Re: Status 100 (Thursday, 26 June)
• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• RE: MUST a client wait for 100 when doing PUT or POST? (Wednesday, 11 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: 1xx Clarification (Monday, 21 April)
• Re: 1xx Clarification (Monday, 21 April)

Jon Knight

• Re: cache-busting document (Tuesday, 10 June)

Jonathan Stark

• Re: A linguistic note on unverifiable transactions (Friday, 25 April)
• Re: FW: Proposed amendment to RFC2109 (Friday, 4 April)

Josh

• Re: OPTIONS method (Sunday, 15 June)
• Re: Proposal: Vary on Cookies (Sunday, 15 June)
• Re: ID: Proxy autoconfig (Friday, 11 April)
• Re: ID: Proxy autoconfig (Tuesday, 8 April)
• Re: Ignore proxy (Wednesday, 2 April)
• Re: Ignore proxy (Wednesday, 2 April)

Josh Cohen

• Re: 305/306 response codes (Thursday, 12 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: 305/306 response codes (Sunday, 8 June)
• OPTIONS method (Saturday, 7 June)
• RE: 305/306 response codes (Saturday, 7 June)
• 305/306 response codes (Friday, 6 June)
• Re: HTTP/1.1 -- who disconnects the session? (Friday, 6 June)
• Re: An experiment in producing RFC1122-style requirements checklist (Monday, 2 June)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Monday, 12 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Saturday, 10 May)
• Re: ftp URL stuff (was MIME multipart/* vs HTTP) (Tuesday, 6 May)
• Re: FTP urls (Tuesday, 6 May)
• FTP urls (Tuesday, 6 May)
• Re: MIME multipart/* vs HTTP (Tuesday, 6 May)
• Re: HTTP State Management Mechanism (Rev1): EndSession attribute (Tuesday, 29 April)
• Re: HTTP/1.1 Pipelining (Sunday, 13 April)
• Re: ID: Proxy autoconfig (Friday, 11 April)
• Re: 1xx Clarification (Friday, 11 April)
• HTTP/1.1 Pipelining (Friday, 11 April)
• Re: webmaster@website (Tuesday, 1 April)

Josh Cohen,685 E. Middlefield; 2nd Floor; Mountain View CA 94043,4157,7134

• Re: SSL tunneling status (Monday, 14 April)

Keith Moore

• from the AD: content-length is invalid within multipart (Wednesday, 7 May)
• Re: IPP>PRO - http comments (Friday, 2 May)
• Re: IPP>PRO - http comments (Friday, 2 May)
• Re: MIME multipart/* vs HTTP (Thursday, 1 May)

Kevin J. Dyer

• Re: Issues-list item "DISPOSITION" (Friday, 25 April)
• Re: Issues-list item "DISPOSITION" (Tuesday, 22 April)

Klaus Weide

• ftp URL stuff (was MIME multipart/* vs HTTP) (Tuesday, 6 May)

Koen Holtman

• Re: 305/306 response codes (Monday, 30 June)
• Re: Proposal: 100-Continue optional under Client control (Monday, 30 June)
• Updated test implementation for TCN available (Friday, 27 June)
• Re: Transient content negotiation (Tuesday, 24 June)
• Re: More thoughts on content negotiation (Saturday, 21 June)
• Re: Transient content negotiation (Friday, 20 June)
• Re: COMMENT: LAST CALL comment (Thursday, 19 June)
• Re: First draft of negotiation requirements document (Wednesday, 18 June)
• Re: First draft of negotiation requirements document (Tuesday, 17 June)
• Re: 305/306 response codes (Tuesday, 17 June)
• Re: 305/306 response codes (Tuesday, 17 June)
• Re: COMMENT: LAST CALL comment (Sunday, 15 June)
• Re: Proposal: Vary on Cookies (Sunday, 15 June)
• Re: Proposal: Vary on Cookies (Friday, 13 June)
• Re: cache-busting and charsets again (Wednesday, 11 June)
• Re: cache-busting document (Wednesday, 11 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST (Wednesday, 11 June)
• Re: New feature negotiation syntax (Tuesday, 10 June)
• Re: New feature negotiation syntax (Tuesday, 10 June)
• Re: draft-ietf-http-negotiation-02.txt (Saturday, 7 June)
• Re: New feature negotiation syntax (Saturday, 7 June)
• Re: New feature negotiation syntax (Friday, 6 June)
• Re: New feature negotiation syntax (Friday, 6 June)
• Re: COMMENT: resolution (Thursday, 5 June)
• Re: New feature negotiation syntax (Thursday, 5 June)
• Re: New feature negotiation syntax (Thursday, 5 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• Re: New feature negotiation syntax (Sunday, 1 June)
• Re: New feature negotiation syntax (Saturday, 31 May)
• Re: New feature negotiation syntax (Friday, 30 May)
• Re: NS, Verisign, Firefly proposal [was Re: Revised charter , (Friday, 30 May)
• Re: Revised charter milestones (Wednesday, 28 May)
• Re: Comment on PEP draft (Wednesday, 28 May)
• Re: New feature negotiation syntax (Wednesday, 28 May)
• Re: Rewrite of feature tag syntax rules (Monday, 26 May)
• New content negotiation draft: draft-ietf-http-negotiation-02.txt (Monday, 26 May)
• Re: notes from previous Editing Group meeting: goals, docking (Sunday, 25 May)
• COMMENT: LAST CALL comment (Sunday, 25 May)
• Call for comments on feature tag syntax (Monday, 19 May)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: PEP Integration in RTSP (Monday, 19 May)
• Re: RANGES (Might be nice to allow 206 response to range request (Monday, 19 May)
• Re: Comment on PEP draft (Monday, 19 May)
• Re: Issue: BYTE-RANGE (Is the right meta-data returned on range (Monday, 19 May)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: Rewrite of feature tag syntax rules (Friday, 16 May)
• Re: Rewrite of feature tag syntax rules (Friday, 16 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: feature negotiation syntax (Wednesday, 14 May)
• Rewrite of feature tag syntax rules (Wednesday, 14 May)
• Re: New feature negotiation syntax (Monday, 12 May)
• Re: feature negotiation syntax (Monday, 12 May)
• New feature negotiation syntax (Tuesday, 6 May)
• Comment on PEP draft (Monday, 5 May)
• Re: A linguistic note on unverifiable transactions (Friday, 25 April)
• A linguistic note on unverifiable transactions (Thursday, 24 April)
• Re: Back from the grave: Unverifiable Transactions and Cookies (Thursday, 24 April)
• Re: Issues-list item "QZERO" (Wednesday, 23 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Wednesday, 23 April)
• Re: Issues-list item "DISPOSITION" (Wednesday, 23 April)
• Re: Issues-list item "DISPOSITION" (Wednesday, 23 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)
• Issues-list item "DISPOSITION" (Sunday, 20 April)
• Issues-list item "QZERO" (Sunday, 20 April)
• Issues-list item "LWS-DELIMITER" (Sunday, 20 April)

Kolics Bertold, University of Veszprem

• Re: Issues-list item "CACHING-CGI" (Thursday, 17 April)
• Re: Request for HTML Draft to support Multi Direction languages. (Saturday, 5 April)

Larry Masinter

• Re: Assigned paths (Friday, 27 June)
• Re: Transient content negotiation (Friday, 20 June)
• Re: First draft of negotiation requirements document (Thursday, 19 June)
• Re: 305/306 response codes (Wednesday, 18 June)
• Re: Proposal: Vary on Cookies (Friday, 13 June)
• Re: cache-busting document (Saturday, 7 June)
• Graham Klyne on content negotiation (Friday, 6 June)
• Re: New feature negotiation syntax (Friday, 6 June)
• Re: COMMENT: LAST CALL comment (Thursday, 5 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• Re: New feature negotiation syntax (Sunday, 1 June)
• Re: New feature negotiation syntax (Saturday, 31 May)
• Re: New feature negotiation syntax (Friday, 30 May)
• Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones (Thursday, 29 May)
• Re: New feature negotiation syntax (Thursday, 29 May)
• Re: Revised charter milestones (Wednesday, 28 May)
• Re: URI -> URL when talking about 'moved ...' (Wednesday, 28 May)
• URI -> URL when talking about 'moved ...' (Wednesday, 28 May)
• Re: New feature negotiation syntax (Wednesday, 28 May)
• Revised charter milestones (Monday, 26 May)
• COMMENT: resolution (Sunday, 25 May)
• Re: HTTP 1.1 Issue: When To Close Connections (Saturday, 24 May)
• notes from previous Editing Group meeting: goals, docking (Saturday, 24 May)
• HTTP Issues LAST CALL; HTTP editing group (Saturday, 24 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 22 May)
• Re: Rewrite of feature tag syntax rules (Monday, 19 May)
• Re: Rewrite of feature tag syntax rules (Saturday, 17 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: feature negotiation syntax (Wednesday, 14 May)
• Re: feature negotiation syntax (Tuesday, 13 May)
• Re: feature negotiation syntax (Tuesday, 13 May)
• "versions" -> Informational RFC (Friday, 9 May)
• Re: New feature negotiation syntax (Friday, 9 May)
• Re: New feature negotiation syntax (Thursday, 8 May)
• feature negotiation syntax (Thursday, 8 May)
• Re: MIME multipart/* vs HTTP (Tuesday, 6 May)
• Re: Accept header and inline images (Saturday, 3 May)
• Re: HTTP State Management Mechanism (Rev1): EndSession attribute (Thursday, 1 May)
• Re: IPP>PRO - http comments (Thursday, 1 May)
• Re: MIME multipart/* vs HTTP (Thursday, 1 May)
• Re: HTTP State Management Mechanism (Rev1): EndSession attribute (Wednesday, 30 April)
• Re: Issues-list item "DISPOSITION" (Thursday, 24 April)
• "last call": draft-ietf-http-versions-01.txt (Monday, 21 April)
• Re: 1xx Clarification (Wednesday, 16 April)
• Re: 1xx Clarification (Wednesday, 16 April)
• privacy platforms (Tuesday, 15 April)
• draft minutes, HTTP-WG meetings April 7 (Friday, 11 April)
• Summary, HTTP-WG meeting in Memphis (Thursday, 10 April)
• Re: 1xx Clarification (Thursday, 10 April)
• Re: Proposed amendment to RFC2109 (Friday, 4 April)
• Re: webmaster@website (Tuesday, 1 April)

Luigi Rizzo

• Re: Question (Wednesday, 11 June)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Wednesday, 23 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)
• Re: Pipelining and compression effect on HTTP/1.1 proxies (Tuesday, 22 April)

Luis Alberto Caceres

• Re: WEB->FAX (Friday, 16 May)
• WEB->FAX (Thursday, 15 May)

M. Hedlund

• Re: draft minutes, HTTP-WG meetings April 7 (Sunday, 13 April)

Malcolm Messiter

• HTTP Download (Saturday, 21 June)

Martin Hamilton

• cache-busting document (Saturday, 7 June)

Martin J. Duerst

• Re: charsets again (Wednesday, 11 June)
• Re: cache-busting and charsets again (Wednesday, 11 June)
• Re: Rewrite of feature tag syntax rules (Friday, 23 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 22 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 22 May)
• Re: Rewrite of feature tag syntax rules (Friday, 16 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: feature negotiation syntax (Wednesday, 14 May)
• Re: feature negotiation syntax (Wednesday, 14 May)
• Re: MIME multipart/* vs HTTP (Wednesday, 30 April)
• Re: Request for HTML Draft to support Multi Direction languages. (Monday, 7 April)

Matthew Rubenstein

• Re: confidentiality and the referer field (Thursday, 26 June)
• Re: confidentiality and the referer field (Thursday, 26 June)

message@marketcom2.com

• Web Site Visibility (Monday, 9 June)

Michael Giroux

• RE: confidentiality and the referer field (Friday, 27 June)
• RE: confidentiality and the referer field (Friday, 27 June)
• Persistent connections, and 1.0 browsers (Friday, 6 June)
• HTTP/1.1 -- who disconnects the session? (Friday, 6 June)
• RE: MIME multipart/* vs HTTP (Thursday, 1 May)
• RE: HTTP State Management Mechanism (Rev1): EndSession attribute (Tuesday, 29 April)
• RE: HTTP State Management Mechanism (Rev1): EndSession attribute (Tuesday, 29 April)
• RE: HTTP State Management Mechanism (Rev1): EndSession attribute (Tuesday, 29 April)
• HTTP State Management Mechanism (Rev1): EndSession attribute (Sunday, 27 April)

Michael S. Fox

• RE: e-mail (Saturday, 5 April)

Mike_Spreitzer.PARC@xerox.com

• Re: URI -> URL when talking about 'moved ...' (Wednesday, 28 May)

Misha Wolf

• Date/time on the Internet (Saturday, 31 May)
• Call for Papers - 11th Unicode Conference - September 1997, California (Wednesday, 2 April)

nemo/Joel N. Weber II

• Re: Origin Servers without Clocks (Tuesday, 22 April)
• Re: Digest Authentication, Netscape, and Microsoft (Tuesday, 15 April)
• Re: Digest Authentication, Netscape, and Microsoft (Tuesday, 15 April)

Nick Ambrose

• RE: MIME multipart/* vs HTTP (Wednesday, 30 April)

owl@owlsnest.com

• Is Your Web Site A Secret? (Thursday, 12 June)

P.Lister@cranfield.ac.uk

• Unidentified subject! (Tuesday, 10 June)
• Re: cache-busting document (Tuesday, 10 June)
• Re: cache-busting document (Tuesday, 10 June)

Patrick Powell

• Re: IPP> Re: MIME multipart/* vs HTTP (Saturday, 3 May)

Paul Hoffman

• Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones (Thursday, 29 May)

Paul Leach

• RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests? (Wednesday, 11 June)
• RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests? (Tuesday, 10 June)

Phillip M Hallam-Baker

• Re: HTTP practice and Year-2000: the bad(?) news (Saturday, 12 April)

Phillip M. Hallam-Baker

• Re: IPP>PRO - http comments (Thursday, 1 May)
• Re: MIME multipart/* vs HTTP (Thursday, 1 May)
• RE: HTTP/1.1-TCP interactions (was Re: HTTP Connection Management(draft-ietf-http-connection-00.txt)) (Monday, 7 April)

Pixieo2@aol.com

• Re: MUST a client wait for 100 when doing PUT or POST? (Thursday, 12 June)

Randy Turner

• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests? (Wednesday, 11 June)

Richard Vermillion

• Re: Proposal: Vary on Cookies (Friday, 13 June)
• Proposal: Vary on Cookies (Thursday, 12 June)

rlgray@raleigh.ibm.com

• Status 100 (Thursday, 26 June)
• Re: An experiment in producing RFC1122-style requirements checklist (Monday, 2 June)
• Memphis followup (Thursday, 17 April)

Rob Lanphier

• PEP Integration in RTSP (Friday, 16 May)

Robert Herriot

• Re: IPP>PRO - http comments (Thursday, 1 May)
• Re: IPP> MIME multipart/* vs HTTP (Wednesday, 30 April)
• Re: IPP>PRO - http comments (Wednesday, 30 April)

Ross Patterson

• Re: confidentiality and the referer field (Thursday, 26 June)
• Re: confidentiality and the referer field (Thursday, 26 June)
• Re: confidentiality and the referer field (Thursday, 26 June)
• Re: confidentiality and the referer field (Thursday, 26 June)
• Re: Assigned paths (Thursday, 26 June)
• Assigned paths (Thursday, 26 June)
• Re: 305/306 response codes (Thursday, 12 June)
• Re: COMMENT: LAST CALL comment (Wednesday, 4 June)
• Re: COMMENT: LAST CALL comment (Wednesday, 4 June)
• Re: An experiment in producing RFC1122-style requirements checklist (Friday, 30 May)
• HTTP 1.1 Issue: 403VS404 (Wednesday, 28 May)
• Re: PEP Integration in RTSP (Saturday, 17 May)
• Re: PEP Integration in RTSP (Friday, 16 May)
• Re: Origin Servers without Clocks (Tuesday, 22 April)

Roy T. Fielding

• Re: Assigned paths (Thursday, 26 June)
• Re: 305/306 response codes (Monday, 16 June)
• Re: COMMENT: LAST CALL comment (Monday, 16 June)
• Re: OPTIONS method (Monday, 16 June)
• Re: COMMENT: LAST CALL comment (Wednesday, 11 June)
• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• Re: cache-busting and charsets again (Wednesday, 11 June)
• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Wednesday, 11 June)
• Re: MUST a client wait for 100 when doing PUT or POST? (Wednesday, 11 June)
• Re: OPTIONS method (Wednesday, 11 June)
• Re: cache-busting and charsets again (Wednesday, 11 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: Rewrite of feature tag syntax rules (Friday, 16 May)
• Re: Rewrite of feature tag syntax rules (Thursday, 15 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Monday, 12 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Monday, 12 May)
• Re: NUDGE: Our piece on Host: and URLs (Fwd) (Saturday, 10 May)
• Re: Issues-list item "QZERO" (Tuesday, 22 April)
• Re: Issues-list item "DISPOSITION" (Tuesday, 22 April)
• Re: mid-course errors (Monday, 21 April)
• Re: 1xx Clarification (Monday, 21 April)
• Re: 1xx Clarification (Monday, 21 April)
• Re: 1xx Clarification (Monday, 21 April)
• No Date in 1xx responses (was Re: Memphis followup) (Friday, 18 April)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 16 April)
• Re: 1xx Clarification (Monday, 14 April)
• Re: 1xx Clarification (Monday, 14 April)
• Re: HTTP/1.1 Pipelining (Monday, 14 April)

Sami Iren

• Question (Monday, 9 June)

Scott Lawrence

• Re: First draft of negotiation requirements document (Tuesday, 17 June)
• Re: MUST a client wait for 100 when doing PUT or POST? (Wednesday, 11 June)
• Re: A new suggestion on 100 CONTINUE (Wednesday, 11 June)
• Re: MUST a client wait for 100 when doing PUT or POST? (Wednesday, 11 June)
• Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)
• Re: 305/306 response codes (Tuesday, 10 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• Re: New feature negotiation syntax (Sunday, 1 June)
• Re: An experiment in producing RFC1122-style requirements checklist (Friday, 30 May)
• Re: Common Gateway Interface (Friday, 30 May)
• Re: New feature negotiation syntax (Sunday, 25 May)
• Re: New feature negotiation syntax (Monday, 12 May)
• Re: IPP> MIME multipart/* vs HTTP (Wednesday, 30 April)
• Re: MIME multipart/* vs HTTP (Wednesday, 30 April)
• Re: MIME multipart/* vs HTTP (Wednesday, 30 April)
• MIME multipart/* vs HTTP (Wednesday, 30 April)
• Re: 1xx Clarification (Tuesday, 22 April)
• Origin Servers without Clocks (Tuesday, 22 April)
• Re: 1xx Clarification (Monday, 21 April)
• Re: Digest Authentication, Netscape, and Microsoft (Thursday, 17 April)
• Re: mid-course errors (Wednesday, 16 April)
• Insisting on a message digest (rfc2069) (Tuesday, 15 April)
• Re: Digest Authentication, Netscape, and Microsoft (Tuesday, 15 April)
• New Proposed Chunked Rules (Monday, 14 April)
• Re: 1xx Clarification (Monday, 14 April)
• Re: 1xx Clarification (Friday, 11 April)
• Re: 1xx Clarification (Friday, 11 April)
• Change to Chunk Length Syntax (Friday, 11 April)

Shel Kaphan

• cache-busting document (Monday, 9 June)

Steve Reiss

• Re: FW: Proposed amendment to RFC2109 (Tuesday, 15 April)

Ted Hardie

• Re: First draft of negotiation requirements document (Thursday, 19 June)
• Re: First draft of negotiation requirements document (Tuesday, 17 June)
• Re: First draft of negotiation requirements document (Tuesday, 17 June)
• First draft of negotiation requirements document (Friday, 13 June)
• Re: New feature negotiation syntax (Friday, 6 June)
• Re: New feature negotiation syntax (Friday, 6 June)
• Re: New feature negotiation syntax (Wednesday, 4 June)
• OPS specification (Wednesday, 28 May)
• Re: New PEP draft available as ID! (Wednesday, 30 April)
• State management (Tuesday, 29 April)
• Re: FW: Proposed amendment to RFC2109 (Friday, 4 April)

The IESG

• Document Action: Use and interpretation of HTTP version numbers to Informational (Wednesday, 14 May)

touch@isi.edu

• Re: Q: protocolls and fault tolerance (Friday, 30 May)
• Re: Q: protocolls and fault tolerance (Friday, 30 May)

Vinod Valloppillil

• RE: Issues-list item "CACHING-CGI" (Wednesday, 16 April)

W.Sylwestrzak@icm.edu.pl

• cache-busting and charsets again (Wednesday, 11 June)
• cache-busting and charsets again (Wednesday, 11 June)
• Re: cache-busting document (Wednesday, 11 June)
• Re: cache-busting document (Saturday, 7 June)

Wingard, Steve

• RE: ISSUE: MUST a client wait for 100 when doing PUT or POST requests? (Tuesday, 10 June)

Wojtek Sylwestrzak

• charsets again (Wednesday, 11 June)
• Re: cache-busting document (Sunday, 8 June)

Yaron Goland

• HTTP/1.1 & Proxies (Tuesday, 1 July)
• RE: 305/306 response codes (Wednesday, 11 June)
• RE: New feature negotiation syntax (Friday, 6 June)
• RE: New feature negotiation syntax (Friday, 6 June)
• RE: New feature negotiation syntax (Friday, 6 June)
• RE: New feature negotiation syntax (Friday, 6 June)
• RE: An experiment in producing RFC1122-style requirements checkli st (Thursday, 29 May)
• RE: PEP Integration in RTSP (Saturday, 24 May)
• RE: PEP Integration in RTSP (Saturday, 24 May)
• RE: PEP Integration in RTSP (Saturday, 24 May)
• RE: PEP Integration in RTSP (Friday, 23 May)
• RE: PEP Integration in RTSP (Friday, 23 May)
• RE: PEP Integration in RTSP (Friday, 23 May)
• RE: New feature negotiation syntax (Friday, 23 May)
• RE: New feature negotiation syntax (Friday, 9 May)
• RE: New PEP draft available as ID! (Wednesday, 30 April)
• RE: 1xx Clarification (Wednesday, 16 April)
• RE: 1xx Clarification (Tuesday, 15 April)
• RE: 1xx Clarification (Tuesday, 15 April)
• RE: 1xx Clarification (Tuesday, 15 April)
• RE: mid-course errors (Tuesday, 15 April)
• 1xx Clarification (Tuesday, 8 April)
• RE: ID: Proxy autoconfig (Tuesday, 8 April)
• RE: ID: Proxy autoconfig (Sunday, 6 April)

Last message date: Tuesday, 1 July 1997 00:14:13 UTC