ietf-http-wg@w3.org from January to March 1996 by author

Albert Lunde

• Re: Non Latin1 charsets (draft-holtman-http-negotiation-00.txt) (Saturday, 2 March)
• Re: URI Pattern Syntax (Saturday, 24 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Saturday, 10 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Saturday, 10 February)
• Re: Round 3: moving HTTP 1.0 to informational (Friday, 9 February)
• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)

Alex Hopmann

• Re: Persistent Connection Question (Wednesday, 27 March)
• Persistent Connection Question (Wednesday, 27 March)
• Re: the Host: saga (Wednesday, 27 March)
• Re: About that Host: header.... (Tuesday, 26 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Thursday, 7 March)
• Re: FW: Number of connections (Friday, 16 February)
• Re: Length - any takers? (Monday, 5 February)
• Re: Length - any takers? (Friday, 2 February)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: Where should Digest go next? (Thursday, 4 January)

Alex Lopez-Ortiz

• Host: header and port number (Tuesday, 26 March)
• Re: Issues Beyond HTTP/1.1 ??? (Saturday, 23 March)
• Issues Beyond HTTP/1.1 ??? (Friday, 22 March)

Alexei Kosut

• Re: About that Host: header.... (Sunday, 24 March)
• Re: I-D ACTION:draft-ietf-http-ses-ext-01.txt (Thursday, 22 February)

Allan M. Schiffman

• Re: Digest Authentication (Monday, 1 January)
• Re: Digest Authentication (Monday, 1 January)

Anawat Chankhunthod

• Re: (DNS) consensus wording (Sunday, 31 March)
• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Thursday, 28 March)
• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Thursday, 28 March)
• Re: (DNS) draft wording for W.G. review. (Thursday, 28 March)
• Re: (DNS) draft wording for W.G. review. (Wednesday, 27 March)
• Re: (DNS) draft wording for W.G. review. (Wednesday, 27 March)

Andrew Wilson

• Re: Apache LogFormat - addition of %v virtual server ID (Thursday, 28 March)

Andy Norman

• Administrivia: digest of list available (Monday, 25 March)
• hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Monday, 4 March)
• Re: archives temporarily moved (Friday, 23 February)
• Re: FTP-able archive of HTTP-WG mail? (Sunday, 7 January)
• Daniel DuBois: More content negotiation (Saturday, 6 January)

Andy Rabagliati

• Apache LogFormat - addition of %v virtual server ID (Thursday, 28 March)

Ari Luotonen

• Re: About that Host: header.... (Tuesday, 19 March)
• Re: About that Host: header.... (Tuesday, 19 March)
• Re: Can proxies rewrite Date:? (Tuesday, 5 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Monday, 4 March)
• Re: URI Pattern Syntax (Friday, 23 February)
• Re: URI Pattern Syntax (Friday, 23 February)

Balint Nagy Endre

• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Sunday, 24 March)
• Re: Host: header and port number (Wednesday, 24 January)
• Re: Host: header and port number (Wednesday, 24 January)

BearHeart / Bill Weinman

• Re: About that Host: header.... (Tuesday, 19 March)
• Re: CGI in HTTP standards documents (Friday, 23 February)
• Re: CGI in HTTP standards documents (Friday, 23 February)
• Re: I-D ACTION:draft-ietf-http-ses-ext-01.txt (Thursday, 22 February)
• Re: New response code (Monday, 19 February)
• Re: New response code (Monday, 19 February)
• Re: Length - any takers? (Monday, 5 February)
• Re: Length - any takers? (Saturday, 3 February)
• Re: Length - any takers? (Friday, 2 February)
• Re: html, http, urls and internationalisation (Sunday, 28 January)
• Re: html, http, urls and internationalisation (Sunday, 28 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)
• Re: Host: header and port number (Tuesday, 23 January)
• Re: state management sub-group status (Sunday, 21 January)

Benjamin Franz

• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: Round 2: moving HTTP 1.0 to informational (Tuesday, 9 January)

Beth Frank

• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Friday, 22 March)
• Re: About that Host: header.... (Tuesday, 19 March)

Bill Janssen

• Re: Auth / APOP / RFC1734 / RFC1731 (Tuesday, 20 February)

Bob Denny

• Re: Some randomness concerning chunked encoding. (Sunday, 24 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Tuesday, 5 March)

Bob Jernigan

• Re: Round 2: moving HTTP 1.0 to informational (Tuesday, 9 January)

Borka Jerman-Blazic

• Re: html, http, urls and internationalisation (Wednesday, 31 January)

Brian Behlendorf

• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Tuesday, 5 March)
• Re: Negotiation issue list (Wednesday, 28 February)
• Re: feature negotiation (Wednesday, 28 February)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: [S.N.Brodie@ecs.soton.ac.uk: HTTP/1.1 Host request-header query] (Saturday, 20 January)

Brian Gaines

• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)
• Re: Caching data returned from POST, and conditional POST (Thursday, 4 January)
• Re: Caching data returned from POST, and conditional POST (Monday, 1 January)
• Re: Caching data returned from POST, and conditional POST (Monday, 1 January)

Carlos Horowicz

• Re: Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Re: FW: Number of connections (Friday, 16 February)
• Re: FW: Number of connections (Friday, 16 February)
• Re: HTTP Working Group 'issues' list (Thursday, 15 February)
• Re: HTTP Working Group 'issues' list (Thursday, 15 February)
• Re: Issue List: CACHEDATE (Wednesday, 14 February)

Christophe Furet

• HTTP protocol and COBOL programs (Tuesday, 19 March)

Cynthia Clark

• Re: draft-ietf-http-v11-spec-01.txt? (Friday, 19 January)

Dan Stromberg - OAC-DCS

• Re: Digest Authentication (Monday, 1 January)

Dan.Oscarsson@malmo.trab.se

• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• html, http, urls and internationalisation (Sunday, 28 January)

Daniel DuBois

• Re: About that Host: header.... (Wednesday, 20 March)
• Re: Variant IDs (Tuesday, 12 March)
• Re: Variant IDs (Monday, 11 March)
• Re: Non Latin1 charsets (draft-holtman-http-negotiation-00.txt) (Friday, 1 March)
• Re: Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: [S.N.Brodie@ecs.soton.ac.uk: HTTP/1.1 Host request-header query] (Friday, 19 January)
• Sample 1.1ish implementation - Free Download Spyglass Server (Tuesday, 16 January)

Daniel LaLiberte

• Re: Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Transparency vs. Performance: survey of opinion (Monday, 26 February)

Daniel W. Connolly

• don't use POST for big GET [was: Dictionaries in HTML ] (Sunday, 4 February)

Daniel, Sonia e Teresa

• Confirm! (Thursday, 7 March)

Dave Kristol

• TRACE: HTTP/1.1 open issue (Tuesday, 5 March)
• draft-kristol-http-state-mgmt-00.txt, .ps (Monday, 26 February)
• Re: Agenda for Transport/Apps BOF (Friday, 23 February)
• Re: URI Pattern Syntax (Friday, 23 February)
• Re: URI Pattern Syntax (Friday, 23 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• more on Digest Auth (Wednesday, 21 February)
• Re: HTTP Working Group 'issues' list (Wednesday, 14 February)
• Re: Signatures and Authentication information must go at end of meesage. (Wednesday, 7 February)
• PostScript version of http-v11-spec-01? (Wednesday, 24 January)
• Re: state management sub-group status (Monday, 22 January)
• state management sub-group status (Saturday, 20 January)

Dave Long

• Re: PUT, DELETE vs. POST (Wednesday, 13 March)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Tuesday, 5 March)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Friday, 23 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Friday, 23 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Friday, 23 February)
• Re: Length - any takers? (Monday, 5 February)
• Re: Describing current practice for 301 and 302 (Wednesday, 31 January)
• Re: safe PUT (Monday, 8 January)
• Re: safe PUT (Wednesday, 3 January)

David Robinson

• Re: proxies rewriting URLs (Monday, 11 March)

David W. Morris

• Re: About that Host: header.... (Thursday, 21 March)
• Re: proxies rewriting URLs (Wednesday, 13 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Wednesday, 13 March)
• Re: Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Re: I-D ACTION:draft-ietf-http-ses-ext-01.txt (Monday, 26 February)
• Re: why no-cache is not reload (Sunday, 18 February)
• Re: Number of connections (was: Re: HTTP Working Group 'issues' list) (Sunday, 18 February)
• Re: Issue List: CACHEDATE (Thursday, 15 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Tuesday, 13 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Sunday, 11 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Sunday, 11 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• HTTP 1.0&1.1 URL safe characters conflict with HTML? (Thursday, 8 February)
• (no subject) (Thursday, 8 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Monday, 5 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Sunday, 4 February)
• Re: Describing current practice for 301 and 302 (Thursday, 1 February)
• Re: Describing current practice for 301 and 302 (Thursday, 1 February)
• Re: Describing current practice for 301 and 302 (Thursday, 1 February)
• Re: Host: header and port number (Wednesday, 24 January)
• Re: Los Angeles scheduling.. (Thursday, 11 January)
• Re: Los Angeles scheduling.. (HTTP) (Thursday, 11 January)
• Re: Caching data returned from POST, and conditional POST (Thursday, 4 January)

Davide Musella (CNR)

• Re: entity header field (Friday, 15 March)
• entity header field (Friday, 15 March)

Dirk.vanGulik

• Re: About that Host: header.... (Tuesday, 19 March)
• Re: ISSUES LIST: Chunked Encoding (Friday, 15 March)

djoko@pusdata.dprin.go.id

• I need more information (Monday, 18 March)

Donald E. Eastlake 3rd

• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Wednesday, 27 March)
• gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Wednesday, 27 March)
• Re: (DNS) draft wording for W.G. review. (Wednesday, 27 March)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• NOW TO SUBSCRIBE AND UNSUBSCRIBE (Thursday, 1 February)
• Re: html, http, urls and internationalisation (Tuesday, 30 January)
• Re: Administrivia: bounced messages (Tuesday, 9 January)
• Re: Where should Digest go next? (Thursday, 4 January)

DONNY TJANDRA

• What is the purpose of Keep alive? (Tuesday, 26 March)

Duane Wessels

• Re: Issues Beyond HTTP/1.1 ??? (Friday, 22 March)
• Re: Number of connections (was: Re: HTTP Working Group 'issues' list) (Thursday, 15 February)

Eric W. Sink

• Re: more on Digest Auth (Thursday, 22 February)
• Where should Digest go next? (Wednesday, 3 January)

Erik van der Poel

• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)

Fisher Mark

• Re: About that Host: header.... (Tuesday, 26 March)
• RE: elaboration on MIME and HTTP issue (Friday, 19 January)
• Re: Where should Digest go next? (Thursday, 4 January)
• RE: safe PUT (Thursday, 4 January)

Francois Yergeau

• Re: Round 3: moving HTTP 1.0 to informational (Monday, 12 February)
• Re: html, http, urls and internationalisation (Monday, 29 January)
• Re: html, http, urls and internationalisation (Sunday, 28 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)

Franz J. Hauck

• Re: Issue List: CACHEDATE (Friday, 16 February)
• Re: Issue List: CACHEDATE (Thursday, 15 February)
• Re: Issue List: CACHEDATE (Wednesday, 14 February)
• Re: Issue List: CACHEDATE (Wednesday, 14 February)
• Issue List: CACHEDATE (Wednesday, 14 February)

Gavin Nicol

• Is it just me.. (Thursday, 15 February)
• Re: Round 3: moving HTTP 1.0 to informational (Monday, 12 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: Round 3: moving HTTP 1.0 to informational (Friday, 9 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Thursday, 8 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Tuesday, 6 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Sunday, 4 February)
• Re: Charsets revisited (Friday, 26 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Charsets revisited (Wednesday, 24 January)
• Re: elaboration on MIME and HTTP issue (Tuesday, 23 January)
• Re: elaboration on MIME and HTTP issue (Friday, 19 January)
• Re: Byte ranges & Document title (question) (Thursday, 18 January)

gdmiis@scut.edu.cn

• help (Wednesday, 31 January)

Gilles Missonnier

• 5th WWW Conference -Paris : REGISTRATION IS NOW OPEN (Wednesday, 24 January)

Glenn Adams

• Re: html, http, urls and internationalisation (Thursday, 1 February)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Charsets revisited (Wednesday, 24 January)
• Re: Byte ranges & Document title (question) (Thursday, 18 January)
• Re: Byte ranges & Document title (question) (Thursday, 18 January)

Greg Stein

• Resend: URI http: specification (Tuesday, 26 March)
• URI http: specification (Monday, 4 March)

hallam@w3.org

• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Wednesday, 27 March)
• Re: (DNS) draft wording for W.G. review. (Wednesday, 27 March)
• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Wednesday, 20 March)
• Re: About that Host: header.... (Tuesday, 19 March)
• Re: ISSUES LIST: Chunked Encoding (Friday, 15 March)
• Re: ISSUES LIST: Chunked Encoding (Friday, 15 March)
• Re: entity header field (Friday, 15 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Wednesday, 13 March)
• Re: proxies rewriting URLs (Tuesday, 12 March)
• Re: proxies rewriting URLs (Monday, 11 March)
• Re: Footers and Chunked (Monday, 11 March)
• Re: Footers and Chunked (Saturday, 9 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Monday, 4 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Monday, 4 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Monday, 4 March)
• Some randomness concerning chunked encoding. (Saturday, 2 March)
• Re: more minor Digest Auth editorial comments (Thursday, 29 February)
• Re: Digesting the digest... (Wednesday, 28 February)
• Re: Digest Auth (I think we have a deal!) (Tuesday, 27 February)
• Re: Where we stand on Digest Authentication (Tuesday, 27 February)
• Re: Digest Auth defending against replay (Tuesday, 27 February)
• Re: Digest Auth defending against replay (Monday, 26 February)
• Re: Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Re: URI Pattern Syntax (Saturday, 24 February)
• Re: URI Pattern Syntax (Saturday, 24 February)
• Re: URI Pattern Syntax (Friday, 23 February)
• Re: hallam@w3.org: Re: Notification for Proxy Caches (Friday, 23 February)
• Re: Three working drafts related to demographics work. (Friday, 23 February)
• Three working drafts related to demographics work. (Thursday, 22 February)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Signatures and Authentication information must go at end of meesage. (Wednesday, 7 February)
• Re: Signatures and Authentication information must go at end of meesage. (Wednesday, 7 February)
• Signatures and Authentication information must go at end of meesage. (Wednesday, 7 February)

Harald.T.Alvestrand@uninett.no

• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Friday, 22 March)
• Re: About that Host: header.... (Thursday, 21 March)
• About that Host: header.... (Sunday, 17 March)
• Re: Agenda for Transport/Apps BOF (Sunday, 25 February)
• Agenda for Transport/Apps BOF (Friday, 23 February)
• Re: Request for meeting at IETF in LA (Thursday, 18 January)

Henrik Frystyk Nielsen

• Re: Digesting headers (Thursday, 29 February)
• Re: HTTP Working Group 'issues' list (Wednesday, 14 February)
• Re: HTTP Working Group 'issues' list (Wednesday, 14 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: Describing current practice for 301 and 302 (Thursday, 1 February)
• Re: Charsets revisited (Wednesday, 24 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: Los Angeles scheduling.. (Thursday, 11 January)

Henry Sanders (Exchange)

• RE: ISSUES LIST: Chunked Encoding (Saturday, 16 March)

hopmann@holonet.net

• Re: Some randomness concerning chunked encoding. (Sunday, 3 March)

http-wg-request@cuckoo.hpl.hp.com

• RE: Digest Auth (I think we have a deal!) (Wednesday, 28 February)
• hallam@w3.org: Re: Notification for Proxy Caches (Friday, 23 February)
• Charles Neerdaels: Notification for Proxy Caches (Friday, 23 February)
• Alex Hopmann: Re: New response code (Tuesday, 20 February)
• Administrivia: bounced messages (Monday, 8 January)

Ian Carr-de Avelon

• Allowing servers to contact proxies (Thursday, 7 March)

Ian Duncan

• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Signatures and Authentication information must go at end of meesage. (Wednesday, 7 February)

Internet-Drafts@cnri.reston.va.us

• I-D ACTION:draft-ietf-http-digest-aa-03.txt (Monday, 25 March)
• I-D ACTION:draft-ietf-http-proxy-note-00.txt (Saturday, 24 February)
• I-D ACTION:draft-ietf-http-session-id-00.txt (Saturday, 24 February)
• I-D ACTION:draft-ietf-http-logfile-00.txt (Saturday, 24 February)
• I-D ACTION:draft-ietf-http-range-retrieval-00.txt (Friday, 23 February)
• I-D ACTION:draft-ietf-http-ses-ext-01.txt (Thursday, 22 February)
• I-D ACTION:draft-ietf-http-v10-spec-05.txt, .ps (Wednesday, 21 February)
• I-D ACTION:draft-ietf-http-v11-spec-01.txt (Monday, 22 January)

Jay Greenberg

• Lynx Client Code (UNIX/C only) (Saturday, 6 January)

Jeff Hostetler

• Re: Where we stand on Digest Authentication (Tuesday, 27 February)
• Status of Digest Authentication (Thursday, 22 February)
• Digest Authentication [Was: Re: 'Basic' Authentication...] (Wednesday, 24 January)

Jeffrey Mogul

• Re: Persistent Connection Question (Wednesday, 27 March)
• Re: About that Host: header.... (Thursday, 21 March)
• Re: Cache validators (Tuesday, 12 March)
• Re: proxies rewriting URLs (Monday, 11 March)
• Re: Can proxies rewrite Date:? (Friday, 8 March)
• Re: Transparency vs. Performance: survey of opinion (Tuesday, 5 March)
• Can proxies rewrite Date:? (Tuesday, 5 March)
• Re: Cache validators (Tuesday, 5 March)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Monday, 4 March)
• Re: why no-cache is not reload (Monday, 19 February)
• Re: HTTP Working Group 'issues' list (Thursday, 15 February)
• Re: Number of connections (was: Re: HTTP Working Group 'issues' list) (Thursday, 15 February)
• Number of connections (was: Re: HTTP Working Group 'issues' list) (Wednesday, 14 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Wednesday, 7 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Monday, 5 February)
• Status report for Caching subgroup (Tuesday, 23 January)
• Persistent-connections subgroup status (Friday, 19 January)
• Re: Caching data returned from POST, and conditional POST (Tuesday, 2 January)

Jeremy_Cath@reading.sterling.com

• Re[2]: Compression of HTML documents over HTTP (Tuesday, 5 March)
• Compression of HTML documents over HTTP (Tuesday, 5 March)

jg@w3.org

• (HOST) (FULLURL) draft of changes for W.G. review. (Friday, 29 March)
• (DNS) consensus wording (Friday, 29 March)
• (MEDIATYPES) consensus. (Friday, 29 March)
• (CODES) Draft additions/changes to section 9.4 for 4xx class status codes. (Friday, 29 March)
• Re: About that Host: header.... (Wednesday, 27 March)
• (PRIVACY) Draft words for W.G. review. (Tuesday, 26 March)
• (SECFILE) Consensus (Tuesday, 26 March)
• (CONTENT) draft wording for W.G. review (Tuesday, 26 March)
• (DNS) draft wording for W.G. review. (Tuesday, 26 March)
• (RFC 1900) Consensus (Tuesday, 26 March)
• Re: About that Host: header.... (Monday, 25 March)
• Process for closing out issues. (Please Read This Message). (Friday, 22 March)
• Re: About that Host: header.... (Thursday, 21 March)
• Proposed structure of HTTP 1.1 document(s). (Monday, 18 March)
• Re: About that Host: header.... (Monday, 18 March)
• Dates for HTTP 1.1 (Wednesday, 13 March)
• As you probably know by now... (schedule and important points) (Tuesday, 12 March)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Round 2: moving HTTP 1.0 to informational (Tuesday, 9 January)

Jim Gettys

• Issues list... (Wednesday, 20 March)

John C Klensin

• Re: About that Host: header.... (Thursday, 21 March)
• Re: About that Host: header.... (Wednesday, 20 March)
• Additional comments on the Host: header.... (Monday, 18 March)

John Franks

• Re: I-D ACTION:draft-ietf-http-digest-aa-03.txt (Monday, 25 March)
• Proposed revision to security considerations (Monday, 25 March)
• RE: proxies rewriting URLs (Friday, 15 March)
• RE: proxies rewriting URLs (Monday, 11 March)
• Re: Digest-MessageDigest doesn't work with proxies (Friday, 1 March)
• Re: Digest-MessageDigest doesn't work with proxies (Friday, 1 March)
• Re: Proxies and Digest-MessageDigest (Friday, 1 March)
• Re: Proxies and Digest-MessageDigest (Thursday, 29 February)
• Digesting headers (Thursday, 29 February)
• Re: Digesting the digest... (Thursday, 29 February)
• Re: more minor Digest Auth editorial comments (Thursday, 29 February)
• Re: Digesting the digest... (Wednesday, 28 February)
• Re: more minor Digest Auth editorial comments (Wednesday, 28 February)
• Re: Digest Auth: mutual? (was Digest Auth (I think we have a deal!)) (Wednesday, 28 February)
• Re: more minor Digest Auth editorial comments (Wednesday, 28 February)
• Digest Auth (I think we have a deal!) (Tuesday, 27 February)
• Where we stand on Digest Authentication (Tuesday, 27 February)
• RE: Digest Auth defending against replay (Tuesday, 27 February)
• RE: Digest Auth defending against replay (Monday, 26 February)
• Re: Digest Auth defending against replay (Monday, 26 February)
• Digest Auth defending against replay (Saturday, 24 February)
• RE: New draft for Digest Authentication (Friday, 23 February)
• New draft for Digest Authentication (Friday, 23 February)
• Re: more on Digest Autho (Thursday, 22 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: Where should Digest go next? (Thursday, 4 January)
• Re: Where should Digest go next? (Wednesday, 3 January)

Joseph Arceneaux

• Re: Digest Authentication (Tuesday, 2 January)

Keld J|rn Simonsen

• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Thursday, 28 March)
• Re: Round 3: moving HTTP 1.0 to informational (Monday, 12 February)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: html, http, urls and internationalisation (Tuesday, 30 January)
• Re: html, http, urls and internationalisation (Tuesday, 30 January)
• Re: (MAITS.496) html, http, urls and internationalisation (Sunday, 28 January)
• Re: html, http, urls and internationalisation (Sunday, 28 January)
• Re: html, http, urls and internationalisation (Sunday, 28 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Charsets revisited (Thursday, 25 January)

kennykb@cobweb.crd.ge.com

• Re: Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Re: HTTP Working Group 'issues' list (Monday, 19 February)

Koen Holtman

• Re: (DNS) consensus wording (Saturday, 30 March)
• Issue: interoperability between HTTP/1.0 and HTTP/1.1 (was: Via Header Field) (Sunday, 24 March)
• Re: About that Host: header.... (Friday, 22 March)
• Re: About that Host: header.... (Wednesday, 20 March)
• Re: About that Host: header.... (Tuesday, 19 March)
• Re: About that Host: header.... (Tuesday, 19 March)
• Content negotiation status (Monday, 18 March)
• Re: HTTP version number (Saturday, 16 March)
• Re: HTTP version number (Wednesday, 13 March)
• Re: Variant IDsg (Tuesday, 12 March)
• Re: Cache validators (Tuesday, 12 March)
• Re: Can proxies rewrite Date:? (Saturday, 9 March)
• Re: Can proxies rewrite Date:? (Thursday, 7 March)
• Re: HTTP version number (Tuesday, 5 March)
• Feature Negotiation Headers and Calculations, v1 (Tuesday, 5 March)
• Re: If-ID and Unless-ID Preconditions (Sunday, 3 March)
• Re: HTTP version number (Sunday, 3 March)
• Re: Non Latin1 charsets (draft-holtman-http-negotiation-00.txt) (Saturday, 2 March)
• Re: Transparency vs. Performance: survey of opinion (Friday, 1 March)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Friday, 1 March)
• Re: Negotiation issue list (Wednesday, 28 February)
• Re: transparency, SHOULD and MUST (Wednesday, 28 February)
• Negotiation issue list (Tuesday, 27 February)
• Re: Transparency vs. Performance: survey of opinion (Tuesday, 27 February)
• Re: feature negotiation (Monday, 26 February)
• Re: Cache validators (Monday, 26 February)
• New content negotiation sections, v4 (long) (Sunday, 25 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Sunday, 25 February)
• Re: Cache validators (Saturday, 24 February)
• Re: Round 4: moving HTTP 1.0 to informational (Saturday, 17 February)
• Accept headers and privacy (Wednesday, 14 February)
• Re: Describing current practice for 301 and 302 (Thursday, 1 February)
• Re: Describing current practice for 301 and 302 (Wednesday, 31 January)
• Describing current practice for 301 and 302 (Tuesday, 30 January)
• Re: safe PUT (Saturday, 6 January)
• Re: Caching data returned from POST, and conditional POST (Monday, 1 January)

Kris Benson

• 'Basic' Authentication... (Saturday, 20 January)

Larry Masinter

• Re: HTTP version number (Saturday, 16 March)
• unnecessary chatter on closed issues (multipart vs chunked) (Saturday, 16 March)
• revised HTTP working group charter (Friday, 15 March)
• Minutes, HTTP working group, 35th IETF (Friday, 15 March)
• Re: proxies rewriting URLs (Wednesday, 13 March)
• Re: proxies rewriting URLs (Wednesday, 13 March)
• Re: Variant IDs (Tuesday, 12 March)
• Re: Cache validators (Tuesday, 12 March)
• DRAFT Minutes, 35th IETF HTTP-WG (Tuesday, 12 March)
• Re: Variant IDs (Tuesday, 12 March)
• Re: Footers and Chunked (Sunday, 10 March)
• Re: Footers and Chunked (Saturday, 9 March)
• [hallam@w3.org: Footers and Chunked ] (Saturday, 9 March)
• HTTP meeting summary (Saturday, 9 March)
• Re: Allowing servers to contact proxies (Friday, 8 March)
• proxies rewriting URLs (Thursday, 7 March)
• PUT, DELETE vs. POST (Thursday, 7 March)
• issue status, last update for a while (Wednesday, 28 February)
• transparency, SHOULD and MUST (Wednesday, 28 February)
• Re: Where we stand on Digest Authentication (Tuesday, 27 February)
• HTTP-WG meeting: Need volunteers (Tuesday, 27 February)
• Draft agenda, HTTP-WG (Tuesday, 27 February)
• Re: Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Re: feature negotiation (Monday, 26 February)
• feature negotiation (Monday, 26 February)
• Transparency vs. Performance: survey of opinion (Monday, 26 February)
• what's with the renaming (Sunday, 25 February)
• more draft renames (Sunday, 25 February)
• HTTP/1.0 submitted for Informational RFC (Sunday, 25 February)
• state management status (Saturday, 24 February)
• please rename draft-ietf-http-logfile-00.txt to draft-hallam-http-logfile-00.txt (Saturday, 24 February)
• WRAPPED (was Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? ) (Saturday, 24 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Saturday, 24 February)
• Re: URI Pattern Syntax (Saturday, 24 February)
• Re: URI Pattern Syntax (Friday, 23 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Friday, 23 February)
• remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Friday, 23 February)
• Digest Authentication editor found (Friday, 23 February)
• Re: CGI in HTTP standards documents (Friday, 23 February)
• CGI in HTTP standards documents (Friday, 23 February)
• Digest Authentication topic closed (Friday, 23 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: agenda for LA HTTP meeting (Thursday, 22 February)
• agenda for LA HTTP meeting (Thursday, 22 February)
• Re: HTTP Working Group 'issues' list (Wednesday, 14 February)
• Re: Issue List: CACHEDATE (Wednesday, 14 February)
• HTTP Working Group 'issues' list (Wednesday, 14 February)
• issue status, etc. (Tuesday, 13 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Tuesday, 13 February)
• Re: Round 3: moving HTTP 1.0 to informational (Monday, 12 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Sunday, 11 February)
• Re: Round 3: moving HTTP 1.0 to informational (Sunday, 11 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Sunday, 11 February)
• Re: Round 3: moving HTTP 1.0 to informational (Saturday, 10 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Saturday, 10 February)
• Re: Round 3: moving HTTP 1.0 to informational (Saturday, 10 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Saturday, 10 February)
• Re: Round 3: moving HTTP 1.0 to informational (Friday, 9 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Monday, 5 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Monday, 5 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Sunday, 4 February)
• Re: Length - any takers? (Saturday, 3 February)
• Re: Length - any takers? (Friday, 2 February)
• Re: Describing current practice for 301 and 302 (Thursday, 1 February)
• Re: Describing current practice for 301 and 302 (Thursday, 1 February)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: html, http, urls and internationalisation (Monday, 29 January)
• Re: html, http, urls and internationalisation (Sunday, 28 January)
• Re: 'Basic' Authentication... (Friday, 26 January)
• Re: Round 3: moving HTTP 1.0 to informational (Friday, 26 January)
• Re: Charsets revisited (Thursday, 25 January)
• status of content-negotiation group (Thursday, 25 January)
• working group process: moderation of HTTP-WG mailing list (Wednesday, 24 January)
• Re: Charsets revisited (Wednesday, 24 January)
• Re: Charsets revisited (Wednesday, 24 January)
• Re: Host: header and port number (Tuesday, 23 January)
• Re: Comments on draft-ietf-v11-spec-00 (Sunday, 21 January)
• Re: 'Basic' Authentication... (Saturday, 20 January)
• draft-ietf-http-v11-spec-01.txt? (Friday, 19 January)
• Re: elaboration on MIME and HTTP issue (Friday, 19 January)
• [S.N.Brodie@ecs.soton.ac.uk: HTTP/1.1 Host request-header query] (Friday, 19 January)
• Re: Request for meeting at IETF in LA (Friday, 19 January)
• subgroup status: please report (Friday, 19 January)
• elaboration on MIME and HTTP issue (Friday, 19 January)
• Request for meeting at IETF in LA (Thursday, 18 January)
• MIME and HTTP (Thursday, 18 January)
• Re: Round 2: moving HTTP 1.0 to informational (Friday, 12 January)
• Los Angeles scheduling.. (Thursday, 11 January)
• intent of POST (Wednesday, 10 January)
• Re: Round 2: moving HTTP 1.0 to informational (Tuesday, 9 January)
• FTP-able archive of HTTP-WG mail? (Friday, 5 January)
• Re: Where should Digest go next? (Thursday, 4 January)
• Re: Digest Authentication (Tuesday, 2 January)

Lou Montulli

• Re: New section for Host (Monday, 18 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Monday, 4 March)
• Re: hallam@w3.org: Netscape Bug or KeepAlive Feature ? (Monday, 4 March)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: Host: header and port number (Wednesday, 24 January)

Luigi Rizzo

• Re: HTTP Working Group 'issues' list (Thursday, 15 February)

M. Hedlund

• Re: I-D ACTION:draft-ietf-http-ses-ext-01.txt (Friday, 23 February)
• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)

Marc Baudoin

• HTTP/1.1 proxy authentication question (Wednesday, 10 January)

Mary Ellen Zurko

• Re: Where should Digest go next? (Friday, 5 January)

Masataka Ohta

• Re: html, http, urls and internationalisation (Thursday, 1 February)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)

Maurizio Codogno

• the Host: saga (Tuesday, 26 March)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Monday, 26 February)
• Re: html, http, urls and internationalisation (Monday, 29 January)

mcmsc@ozemail.com.au

• (no subject) (Wednesday, 6 March)

Mike Meyer

• draft-ietf-http-logfile-00.txt and multiple directives (Saturday, 16 March)
• Re: URI Pattern Syntax (Friday, 23 February)
• Re: Length - any takers? (Friday, 2 February)

Mike_Spreitzer.PARC@xerox.com

• Re: html, http, urls and internationalisation (Wednesday, 31 January)

Mirsad Todorovac

• Re: Compression of HTML documents over HTTP (Tuesday, 5 March)
• Re: Non Latin1 charsets (draft-holtman-http-negotiation-00.txt) (Friday, 1 March)
• Re: Non Latin1 charsets (draft-holtman-http-negotiation-00.txt) (Friday, 1 March)
• Re: HTTP-WG meeting: Need volunteers (Tuesday, 27 February)
• Re: I-D ACTION:draft-ietf-http-ses-ext-01.txt (Thursday, 22 February)
• Re: HTTP/1.0 Draft 05 now available (Tuesday, 20 February)
• Re: New response code (Monday, 19 February)
• Re: Byte ranges & Document title (question) (Thursday, 18 January)
• Byte ranges & Document title (question) (Thursday, 18 January)

Mordechai T. Abzug

• Re: New response code (Monday, 19 February)

Murray Altheim

• Re: Negotiation issue list (Tuesday, 27 February)
• Re: feature negotiation (Monday, 26 February)

Ned Freed

• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Wednesday, 27 March)
• Re: feature negotiation (Monday, 26 February)
• Re: more on Digest Auth (Friday, 23 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: APOP - authentication.. (Wednesday, 21 February)
• Re: APOP - authentication.. (Wednesday, 21 February)
• Re: APOP - authentication.. (Tuesday, 20 February)
• Re: RFC1734 (Tuesday, 20 February)
• Re: Other transfer codings (Tuesday, 20 February)
• Re: Round 4: moving HTTP 1.0 to informational (Saturday, 17 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Los Angeles scheduling.. (Thursday, 11 January)
• Re: Where should Digest go next? (Thursday, 4 January)
• Re: Digest Authentication (Tuesday, 2 January)
• Re: Digest Authentication (Tuesday, 2 January)
• Re: Digest Authentication (Monday, 1 January)

Neil Christie

• subscribe (Saturday, 24 February)

Neil Katin

• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)

Nickolay Saukh

• Re: Non Latin1 charsets (draft-holtman-http-negotiation-00.txt) (Friday, 1 March)
• Re: Non Latin1 charsets (draft-holtman-http-negotiation-00.txt) (Friday, 1 March)
• Non Latin1 charsets (draft-holtman-http-negotiation-00.txt) (Friday, 1 March)
• Re: HTTP Working Group 'issues' list (Monday, 19 February)
• Re: HTTP Working Group 'issues' list (Monday, 19 February)
• Re: Round 3: moving HTTP 1.0 to informational (Monday, 12 February)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Charsets revisited (Thursday, 25 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: Charsets revisited (Wednesday, 24 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: Charsets revisited (Wednesday, 24 January)
• Re: Charsets revisited (Wednesday, 24 January)
• Charsets revisited (Tuesday, 23 January)
• Re: elaboration on MIME and HTTP issue (Tuesday, 23 January)

northlan@gate.net

• Re: Digest Authentication (Tuesday, 2 January)

Owen Rees

• Re: Other transfer codings (Tuesday, 20 February)

Paul A Vixie

• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Thursday, 28 March)
• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Thursday, 28 March)
• Re: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Wednesday, 27 March)

Paul Hoffman

• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Sunday, 24 March)
• Re: About that Host: header.... (Friday, 22 March)
• Re: About that Host: header.... (Wednesday, 20 March)
• Re: About that Host: header.... (Tuesday, 19 March)
• Re: Transparency vs. Performance: survey of opinion (Tuesday, 27 February)
• Re: Round 4: moving HTTP 1.0 to informational (Saturday, 17 February)
• Round 4: moving HTTP 1.0 to informational (Friday, 16 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Length - any takers? (Friday, 2 February)
• Re: Describing current practice for 301 and 302 (Wednesday, 31 January)
• Re: Describing current practice for 301 and 302 (Tuesday, 30 January)
• Round 3: moving HTTP 1.0 to informational (Friday, 26 January)
• Quasi-report from the extensions subgroup (Friday, 19 January)
• Re: Round 2: moving HTTP 1.0 to informational (Thursday, 11 January)
• Round 2: moving HTTP 1.0 to informational (Monday, 8 January)
• Re: Where should Digest go next? (Thursday, 4 January)

Paul Leach

• RE: gethostbyname (was Re: (DNS) draft wording for W.G. review. ) (Wednesday, 27 March)
• RE: About that Host: header.... (Tuesday, 19 March)
• RE: HTTP meeting summary (Monday, 11 March)
• Re: Variant IDs (Tuesday, 12 March)
• FW: "Value" caches (was Can proxies rewrite Date:?) (Monday, 11 March)
• Re: Variant IDs (Monday, 11 March)
• RE: proxies rewriting URLs (Monday, 11 March)
• FW: "Value" caches (was Can proxies rewrite Date:?) (Saturday, 9 March)
• Re: Can proxies rewrite Date:? (Friday, 8 March)
• RE: proxies rewriting URLs (Friday, 8 March)
• Re: Can proxies rewrite Date:? (Friday, 8 March)
• RE: Variant IDs (Sunday, 3 March)
• Variant IDs (Saturday, 2 March)
• Re: Digest-MessageDigest doesn't work with proxies (Saturday, 2 March)
• Digest-MessageDigest doesn't work with proxies (Friday, 1 March)
• Re: Proxies and Digest-MessageDigest (Friday, 1 March)
• Digest-MessageDigest doesn't work with proxies (Friday, 1 March)
• Re: Proxies and Digest-MessageDigest (Thursday, 29 February)
• Proxies and Digest-MessageDigest (Thursday, 29 February)
• Re: more minor Digest Auth editorial comments (Thursday, 29 February)
• Proxies and Digest Auth (Thursday, 29 February)
• Re: more minor Digest Auth editorial comments (Thursday, 29 February)
• Re: Digesting the digest... (Thursday, 29 February)
• Re: Digesting the digest... (Thursday, 29 February)
• Re: more minor Digest Auth editorial comments (Thursday, 29 February)
• Re: Digest Auth: mutual? (was Digest Auth (I think we have a deal!)) (Wednesday, 28 February)
• Re: more minor Digest Auth editorial comments (Wednesday, 28 February)
• more minor Digest Auth editorial comments (Wednesday, 28 February)
• Digest Auth: mutual? (was Digest Auth (I think we have a deal!)) (Tuesday, 27 February)
• Digest Auth editorial comments (Tuesday, 27 February)
• RE: Digest Auth (I think we have a deal!) (Tuesday, 27 February)
• FW: Digest Auth defending against replay (Tuesday, 27 February)
• RE: Where we stand on Digest Authentication (Tuesday, 27 February)
• Re: Transparency vs. Performance: survey of opinion (Tuesday, 27 February)
• Re: Digest Auth defending against replay (Tuesday, 27 February)
• RE: Digest Auth defending against replay (Tuesday, 27 February)
• RE: Digest Auth defending against replay (Monday, 26 February)
• RE: New draft for Digest Authentication (Monday, 26 February)
• RE: New draft for Digest Authentication (Saturday, 24 February)
• RE: New draft for Digest Authentication (Friday, 23 February)
• RE: New draft for Digest Authentication (Friday, 23 February)
• Re: more on Digest Autho (Thursday, 22 February)
• (no subject) (Thursday, 22 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Thursday, 22 February)
• FW: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Thursday, 22 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: more on Digest Auth (Wednesday, 21 February)
• Re: APOP - authentication.. (Wednesday, 21 February)
• Re: APOP - authentication.. (Wednesday, 21 February)
• Re: APOP - authentication.. (Tuesday, 20 February)
• Re: APOP - authentication.. (Tuesday, 20 February)
• Re: FW: Number of connections (Friday, 16 February)
• Re: FW: Number of connections (Friday, 16 February)
• Re: FW: Number of connections (Friday, 16 February)
• FW: Number of connections (Thursday, 15 February)

Peter J Churchyard

• Re: Digesting the digest... (Thursday, 29 February)
• Re: Digesting the digest... (Wednesday, 28 February)
• Digesting the digest... (Wednesday, 28 February)
• Re: APOP - authentication.. (Wednesday, 21 February)
• comments on draft-ietf-http-digest-aa-02.txt (Tuesday, 20 February)
• Auth / APOP / RFC1734 / RFC1731 (Tuesday, 20 February)
• Re: RFC1734 (Tuesday, 20 February)
• Minimal compliance... (Tuesday, 20 February)
• Re: Other transfer codings (Tuesday, 20 February)
• Re: APOP - authentication.. (Tuesday, 20 February)
• Re: APOP - authentication.. (Tuesday, 20 February)
• Re: APOP - authentication.. (Tuesday, 20 February)
• APOP - authentication.. (Monday, 19 February)
• Other transfer codings (Monday, 19 February)
• Re: HTTP 1.0 & 1.1 URL safe characters conflict with HTML? (Thursday, 8 February)
• Re: Authentication - with authentication points. (Thursday, 8 February)
• Re: Length - any takers? (Friday, 2 February)
• Length - any takers? (Thursday, 1 February)
• Authentication - with authentication points. (Wednesday, 31 January)
• Re: html, http, urls and internationalisation (Wednesday, 31 January)
• Re: 'Basic' Authentication... (Saturday, 27 January)
• Re: 'Basic' Authentication... (Friday, 26 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)
• Authentication in HTTP 1.1 (Wednesday, 24 January)
• Re: Where should Digest go next. (Sunday, 21 January)
• comments on proxy-authenticate. (Sunday, 21 January)
• Comments on draft-ietf-v11-spec-00 (Sunday, 21 January)

Phillip M. Hallam-Baker

• URI Pattern Syntax (Friday, 23 February)
• Re: Where should Digest go next? (Wednesday, 17 January)

pjc@tis.com

• HTTP-WG Mailing List Archive for Q1, 1996: Re: URI Pattern Syntax (Monday, 26 February)
• Re: Digest Auth defending against replay (Monday, 26 February)

Ravi Shankar

• Question re. OPTIONS, ALLOW (Sunday, 25 February)

Rich Salz

• Re: URI Pattern Syntax (Friday, 23 February)
• Re: URI Pattern Syntax (Friday, 23 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Friday, 23 February)

Rob McCool

• Re: Host: header and port number (Wednesday, 24 January)
• Re: Host: header and port number (Tuesday, 23 January)
• Host: header and port number (Tuesday, 23 January)

Robert B. Denny

• Re: Where should Digest go next? (Wednesday, 3 January)

Rohit Khare

• Re: HTTP version number (Friday, 8 March)
• Re: Question re. OPTIONS, ALLOW (Thursday, 29 February)
• PEP Draft 2 available (Tuesday, 27 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Saturday, 24 February)
• Re: remove WRAPPED? (Saturday, 24 February)

Roy T. Fielding

• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Monday, 25 March)
• Re: About that Host: header.... (Sunday, 24 March)
• Via Header Field (replaces Forwarded) (Sunday, 24 March)
• Re: HTTP version number (Saturday, 16 March)
• New section for Host (Saturday, 16 March)
• UCI archives will be down sometime Tuesday (Monday, 11 March)
• Re: Variant IDs (Monday, 11 March)
• Re: HTTP version number (Monday, 11 March)
• Re: Cache validators (Monday, 11 March)
• Re: proxies rewriting URLs (Monday, 11 March)
• Re: HTTP version number (Monday, 4 March)
• Re: If-ID and Unless-ID Preconditions (Monday, 4 March)
• HTTP version number (Friday, 1 March)
• Re: Transparency vs. Performance: survey of opinion (Thursday, 29 February)
• If-ID and Unless-ID Preconditions (Thursday, 29 February)
• Re: Question re. OPTIONS, ALLOW (Thursday, 29 February)
• Re: Transparency vs. Performance: survey of opinion (Thursday, 29 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Thursday, 29 February)
• Re: more minor Digest Auth editorial comments (Thursday, 29 February)
• Re: Cache validators (Sunday, 25 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Sunday, 25 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Saturday, 24 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Friday, 23 February)
• archives temporarily moved (Thursday, 22 February)
• Re: Cache validators (Thursday, 22 February)
• Re: Other transfer codings (Tuesday, 20 February)
• Re: APOP - authentication.. (Tuesday, 20 February)
• Re: APOP - authentication.. (Tuesday, 20 February)
• Re: Other transfer codings (Tuesday, 20 February)
• Re: Authentication - with authentication points. (Tuesday, 20 February)
• Re: HTTP/1.0 Draft 05 now available (Tuesday, 20 February)
• HTTP/1.0 Draft 05 now available (Monday, 19 February)
• Re: why no-cache is not reload (Sunday, 18 February)
• Re: why no-cache is not reload (Saturday, 17 February)
• why no-cache is not reload (Friday, 16 February)
• Re: HTTP Working Group 'issues' list (Thursday, 15 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Monday, 12 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Monday, 12 February)
• Re: Round 3: moving HTTP 1.0 to informational (Monday, 12 February)
• Re: Round 3: moving HTTP 1.0 to informational (Sunday, 11 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Sunday, 11 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Saturday, 10 February)
• Re: HTTP 1.0&1.1 URL safe characters conflict with HTML? (Friday, 9 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: Round 3: moving HTTP 1.0 to informational (Friday, 9 February)
• Re: don't use POST for big GET [was: Dictionaries in HTML ] (Friday, 9 February)
• Re: Round 3: moving HTTP 1.0 to informational (Thursday, 8 February)
• Re: Signatures and Authentication information must go at end of meesage. (Wednesday, 7 February)
• Re: PostScript version of http-v11-spec-01? (Friday, 26 January)
• Re: Round 2: moving HTTP 1.0 to informational (Thursday, 11 January)
• Re: intent of POST (Wednesday, 10 January)
• Re: FTP-able archive of HTTP-WG mail? (Sunday, 7 January)

Sankar Virdhagriswaran, Crystaliz, Inc.

• Re: Three working drafts related to demographics work. (Friday, 23 February)

Shel Kaphan

• Issues Beyond HTTP/1.1 ??? (Saturday, 23 March)
• Re: proxies rewriting URLs (Monday, 11 March)
• Re: Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Transparency vs. Performance: survey of opinion (Monday, 26 February)
• Re: remove PATCH, COPY, MOVE, DELETE, etc.? Upgrade? (Saturday, 24 February)
• Alex Hopmann: Re: New response code (Tuesday, 20 February)
• Re: New response code (Monday, 19 February)
• Re: why no-cache is not reload (Saturday, 17 February)
• Re: Data Integrity (Thursday, 15 February)
• Data Integrity (Thursday, 15 February)
• Re: Issue List: CACHEDATE (Thursday, 15 February)
• Re: Issue List: CACHEDATE (Thursday, 15 February)
• Re: Issue List: CACHEDATE (Wednesday, 14 February)
• Re: Host: header and port number (Wednesday, 24 January)
• Re: Host: header and port number (Tuesday, 23 January)
• Re: Caching data returned from POST, and conditional POST (Thursday, 4 January)
• Re: Caching data returned from POST, and conditional POST (Monday, 1 January)

Simon Spero

• Re: agenda for LA HTTP meeting (Thursday, 22 February)
• Re: Number of connections (was: Re: HTTP Working Group 'issues' list) (Thursday, 15 February)
• Re: Signatures and Authentication information must go at end of meesage. (Thursday, 8 February)
• Re: Caching data returned from POST, and conditional POST (Monday, 1 January)

smb@research.att.com

• Re: Digest Authentication (Monday, 1 January)

Ted Hardie

• Re: ISSUES LIST: Chunked Encoding (Friday, 15 March)
• Re: ISSUES LIST: Chunked Encoding (Friday, 15 March)
• ISSUES LIST: Chunked Encoding (Friday, 15 March)
• Re: APOP - authentication.. (Wednesday, 21 February)
• Re: why no-cache is not reload (Friday, 16 February)
• Re: Data Integrity (Thursday, 15 February)
• Re: Data Integrity (Thursday, 15 February)
• Re: Data Integrity (Thursday, 15 February)
• Data Integrity (Thursday, 15 February)
• Re: HTTP Working Group 'issues' list (Wednesday, 14 February)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)

Tel 91115

• (no subject) (Thursday, 25 January)

Tim Berners-Lee

• Re: Proposal on removing Content Negotiation from http 1.1 (Thursday, 25 January)
• Re: Proposal on removing Content Negotiation from http 1.1 (Wednesday, 24 January)

Tim Greenwood

• Re: Charsets revisited (Wednesday, 24 January)
• Re: Charsets revisited (Wednesday, 24 January)

Tom Loosemore

• subscribe (Tuesday, 12 March)

Walter Schmid

• Re: 5th WWW Conference -Paris : REGISTRATION IS NOW OPEN (Wednesday, 31 January)

yergeau@alis.ca

• Re: Round 3: moving HTTP 1.0 to informational (Sunday, 11 February)

Last message date: Saturday, 30 March 1996 17:59:10 UTC