ietf-http-wg@w3.org from July to September 1997 by author

Albert Lunde

• Re: some thoughts on extensions on REQUEST line. (Wednesday, 24 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: HTTP status codes (Wednesday, 23 July)

Alfred Brock

• Re: HTTP-WG new charter milestones (Thursday, 31 July)

Andreas Brusinsky

• Q: Methods and Headers? (Monday, 11 August)
• Q:Which headers go with which Methods? (Friday, 8 August)
• Streams connected to http responses? (Monday, 28 July)
• Q: HOWTO use different transmission schemes? (Monday, 21 July)
• Q: About transmission schemes ? (Thursday, 17 July)

Andrew Daviel

• RE: Compressing HTML (Wednesday, 10 September)
• Re: Forcing to another page to load (Sunday, 6 July)
• Re: Interesting stats on the prevalence of bogus Last-Modified times (Friday, 4 July)
• Re: GET and referer security considerations (Wednesday, 2 July)

Andy Norman

• Administriva: http-wg mailing list and spammers (Thursday, 7 August)

Ari Luotonen

• Re: SSL Tunneling; Informational RFC; Last call? (Tuesday, 16 September)
• SSL Tunneling; Informational RFC; Last call? (Friday, 12 September)
• Re: Basic Authentication behavior (Monday, 8 September)
• Re: Basic Authentication behavior (Monday, 8 September)
• Re: RE-VERSION (Thursday, 4 September)
• Re: Basic Authentication behavior (Tuesday, 2 September)
• Re: 305/306 (Wednesday, 23 July)

Arthur Bierer

• RE: 301/302 (Wednesday, 30 July)

Ben Laurie

• Re: indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)
• Re: Last-Modified in chunked footer (Monday, 15 September)
• Re: 301/302 (Friday, 5 September)
• Re: DATE-IF-MODIFIED (Friday, 5 September)
• Re: 301/302 (Friday, 5 September)
• Re: Spelling of "cachable" (Wednesday, 3 September)
• Re: a positive "no thanks" to cookies? (Monday, 11 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: 301/302 (Friday, 1 August)
• Re: 301/302 (Friday, 1 August)
• Re: 301/302 (Thursday, 31 July)
• Re: 301/302 (Wednesday, 30 July)
• Re: 301/302 (Wednesday, 30 July)
• Re: Q: About transmission schemes ? (Thursday, 17 July)

Benjamin Franz

• Re: a positive "no thanks" to cookies? (Monday, 11 August)

Bob Briscoe

• Re: RETRY-AFTER HTTP working group issue... (Thursday, 24 July)

Bob Jernigan

• Re: Spelling of "cachable" (Tuesday, 2 September)

Choi, Hyoung-Kee

• TCP spoofing (Friday, 5 September)

Dan Wing

• Re: Interest in standard HTTP headers for specifying client (Saturday, 20 September)

Dave Kristol

• Re: draft-ietf-http-state-man-mec-03: $Version and path (Tuesday, 23 September)
• Re: draft-ietf-http-state-man-mec-03: $Version and path (Tuesday, 23 September)
• Re: draft-ietf-http-state-man-mec-03: $Version and path (Monday, 22 September)
• Re: I-D ACTION:draft-ietf-http-req-sum-00.txt (Friday, 19 September)
• Re: draft-ietf-http-state-man-mec-03: $Version and path (Thursday, 18 September)
• RE: comments on jaye-trust-state-01 (Thursday, 18 September)
• Content-Coding on POST (Thursday, 11 September)
• Re: Last-Modified in chunked footer (Monday, 8 September)
• Re: 301/302 (Monday, 8 September)
• comments on jaye-trust-state-01 (Tuesday, 19 August)
• Re: draft-ieft-http-options-00.txt (Sunday, 10 August)
• draft-ieft-http-options-00.txt (Thursday, 7 August)
• Re: Set-Cookie2: "additive" vs. "independent" (Tuesday, 29 July)
• Re: Set-Cookie2: "additive" vs. "independent" (Tuesday, 29 July)
• Re: [Fwd: 301/302] (Tuesday, 29 July)
• Re: [Fwd: 301/302] (Tuesday, 29 July)
• Re: an (unofficial) cookie draft (Tuesday, 29 July)
• Set-Cookie2: "additive" vs. "independent" (Tuesday, 29 July)
• Re: Comment-URL question (Monday, 28 July)
• Re: Comment-URL question (Monday, 28 July)
• an (unofficial) cookie draft (Friday, 25 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Tuesday, 22 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Tuesday, 22 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 16 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Sunday, 13 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard (Saturday, 12 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Tuesday, 8 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Thursday, 3 July)

David Jablon

• Re: http-digest-aa-rev-00.txt (Thursday, 7 August)
• Re: http-digest-aa-rev-00.txt (Thursday, 7 August)
• Re: http-digest-aa-rev-00.txt (Wednesday, 6 August)
• Re: http-digest-aa-rev-00.txt (Wednesday, 6 August)

David W. Morris

• RE: Last-Modified in chunked footer (Tuesday, 16 September)
• Revised UA HINT Draft Submitted (Tuesday, 16 September)
• Re: indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)
• Re: indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)
• Re: 301/302 (Wednesday, 3 September)
• RE: 301/302 (Wednesday, 3 September)
• Re: Basic Authentication behavior (Tuesday, 2 September)
• Re: 301/302 (Friday, 29 August)
• Re: a positive "no thanks" to cookies? (Monday, 11 August)
• Re: RE-VERSION (Saturday, 9 August)
• Re: RE-VERSION (Friday, 8 August)
• RE: multipart/byteranges (Tuesday, 5 August)
• RE: Using Content-Encoding and Content-Disposition together (Tuesday, 5 August)
• Re: multipart/byteranges (Monday, 4 August)
• Re: agenda for Munich (Friday, 1 August)
• Re: 301/302 (Friday, 1 August)
• Re: 301/302 (Wednesday, 30 July)
• Re: New Editorial issue MESSAGE-BODY (Wednesday, 30 July)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 30 July)
• Re: Set-Cookie2: "additive" vs. "independent" (Wednesday, 30 July)
• Re: [Fwd: 301/302] (Wednesday, 30 July)
• Re: Set-Cookie2: "additive" vs. "independent" (Tuesday, 29 July)
• Re: Set-Cookie2: "additive" vs. "independent" (Tuesday, 29 July)
• Re: an (unofficial) cookie draft (Tuesday, 29 July)
• Re: Comment-URL question (Tuesday, 29 July)
• Re: Comment-URL question (Monday, 28 July)
• Re: Removing CommentURL (Monday, 28 July)
• Re: State Management pre-draft - combinational requirement (Sunday, 27 July)
• Re: Removing CommentURL (Sunday, 27 July)
• Re: Removing CommentURL (Saturday, 26 July)
• Re: Removing CommentURL (Saturday, 26 July)
• Re: Removing CommentURL (Saturday, 26 July)
• Feedback on: draft-cohen-http305306-02.txt (Friday, 25 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Friday, 25 July)
• Re: The significance of Cookies (Wednesday, 23 July)
• Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Tuesday, 22 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Tuesday, 22 July)
• Re: STATUS100 Re: Proposed resolution (Friday, 18 July)
• Re: STATUS100 Re: Proposed resolution (Friday, 18 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Thursday, 17 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Tuesday, 15 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Monday, 14 July)
• Re: Summary of STATUS100 issue (Thursday, 10 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Thursday, 10 July)
• Re: ISSUE VARY: Proposed wording (Thursday, 10 July)
• Re: Is 100-Continue hop-by-hop? (Thursday, 10 July)
• Re: Refresh, non-standard headers, [was Re: Forcing to another page to load] (Tuesday, 8 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Friday, 4 July)
• Re: Proposal: 100-Continue optional under Client control (Friday, 4 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Friday, 4 July)
• Re: Proposal: 100-Continue optional under Client control (Friday, 4 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Friday, 4 July)
• Re: GET and referer security considerations (Friday, 4 July)
• Re: GET and referer security considerations (Thursday, 3 July)
• Re: GET and referer security considerations (Tuesday, 1 July)

debbie eidelman

• Re: Forcing to another page to load (Sunday, 6 July)

Donald Neal

• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Thursday, 10 July)

Dongfan Chen

• exit (Thursday, 17 July)

Eric Prud'hommeaux

• [Announce] PEP demo at w3c site (Monday, 21 July)

Fisher Mark

• RE: Globally unique e-tags, if-match on content-ID, etc. (Thursday, 18 September)
• RE: FW: revised trusted cookie spec (Tuesday, 19 August)

Foteos Macrides

• Re: draft-ietf-http-state-man-mec-03: $Version and path (Tuesday, 23 September)
• Re: SSL Tunneling; Informational RFC; Last call? (Saturday, 20 September)
• Re: SSL Tunneling; Informational RFC; Last call? (Friday, 19 September)
• Re: SSL Tunneling; Informational RFC; Last call? (Wednesday, 17 September)
• Re: Basic Authentication behavior (Tuesday, 9 September)
• Re: Basic Authentication behavior (Monday, 8 September)
• Re: Basic Authentication behavior (Monday, 8 September)
• Re: Basic Authentication behavior (Monday, 8 September)
• Re: Basic Authentication behavior (Sunday, 7 September)
• Re: 301/302 (Friday, 5 September)
• Re: 301/302 (Thursday, 4 September)
• Re: 301/302 (Thursday, 4 September)
• Re: 301/302 (Thursday, 4 September)
• Re: 301/302 (Thursday, 4 September)
• Re: 301/302 (Thursday, 4 September)
• Issue SAFE (Monday, 1 September)
• Re: 301/302 (Sunday, 31 August)
• Re: 301/302 (Friday, 29 August)
• Re: 301/302 (Friday, 29 August)
• Re: FW: revised trusted cookie spec (Tuesday, 19 August)
• Re: FW: revised trusted cookie spec (Tuesday, 19 August)
• Re: FW: revised trusted cookie spec (Monday, 18 August)
• Re: FW: revised trusted cookie spec (Monday, 18 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: Using Content-Encoding and Content-Disposition together (Thursday, 7 August)
• Re: Using Content-Encoding and Content-Disposition together (Thursday, 7 August)
• Re: Using Content-Encoding and Content-Disposition together (Thursday, 7 August)
• Re: 301/302 (Friday, 1 August)
• Re: HTTP-WG new charter milestones (Thursday, 31 July)
• Re: 301/302 (Wednesday, 30 July)
• Re: The meaning of 301 (was Re: 301/302) (Wednesday, 30 July)
• Re: 301/302 (Wednesday, 30 July)
• Re: 301/302 (Tuesday, 29 July)
• Re: Set-Cookie2: "additive" vs. "independent" (Tuesday, 29 July)
• Re: Set-Cookie2: "additive" vs. "independent" (Tuesday, 29 July)
• Re: Removing CommentURL (Sunday, 27 July)
• Re: Removing CommentURL (Sunday, 27 July)
• State Management pre-draft - combinational requirement (Saturday, 26 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Thursday, 24 July)
• Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Tuesday, 22 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Thursday, 17 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 16 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1)" to Propo (Saturday, 12 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Friday, 11 July)
• Re: SAFE, UAHINT and other things not part of HTTP/1.1 now (Monday, 7 July)
• Re: GET and referer security considerations (Wednesday, 2 July)

Gisle Aas

• Re: draft-ietf-http-state-man-mec-03: $Version and path (Tuesday, 23 September)
• Re: draft-ietf-http-state-man-mec-03: $Version and path (Friday, 19 September)
• draft-ietf-http-state-man-mec-03: $Version and path (Monday, 15 September)

Graham Klyne

• Re: Interest in standard HTTP headers for specifying client display attributes? (Thursday, 18 September)
• Re: Spelling of "cachable" (Tuesday, 2 September)
• Re: draft-ietf-http-feature-reg-01.txt (Tuesday, 15 July)
• Re: New feature tag registration drafts available (Tuesday, 15 July)
• Re: draft-ietf-http-negotiation-02.txt (Tuesday, 15 July)
• TSPECIALS: another nit (Friday, 11 July)
• Re: New feature tag registration drafts available (Friday, 11 July)
• Re: New feature tag registration drafts available (Thursday, 10 July)
• Re: draft-ietf-http-feature-reg-01.txt (Thursday, 10 July)
• Re: Content negotiation requirements (Monday, 7 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Content negotiation requirements (Friday, 4 July)
• Re: ISSUE CONTENT-ENCODING: Proposed wording (Thursday, 3 July)
• Re: draft-ietf-http-negotiation-02.txt (Thursday, 3 July)
• Re: HTTP/1.1 & Proxies (Thursday, 3 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: Assigned paths (Tuesday, 1 July)

Gregory J. Woodhouse

• Re: Proposed resolution for the STATUS100 issue (Friday, 18 July)
• Re: STATUS100 Re: Proposed resolution (Thursday, 17 July)

hedlund

• Re: 301/302 (Thursday, 4 September)
• Re: FW: revised trusted cookie spec (Tuesday, 19 August)
• Re: a positive "no thanks" to cookies? (Sunday, 10 August)

Henning Schulzrinne

• HTTP and friends status codes (Friday, 25 July)

Henning Schulzrinne (BL)

• HTTP status codes (Wednesday, 23 July)

Henrik Frystyk Nielsen

• Issue 1310_CACHE (Wednesday, 30 July)
• ISSUE: 403vs404 (Wednesday, 30 July)
• Re: ISSUE VARY: Proposed wording (Wednesday, 30 July)
• Re: ISSUE VARY: Proposed wording (Wednesday, 30 July)
• Re: Another try at OPTIONS (Wednesday, 30 July)
• ISSUE PROXY-AUTHORIZATION: Proposal wording (Thursday, 17 July)
• Re: ISSUE VARY: Proposed wording (Thursday, 17 July)
• New version of PEP specification available (Tuesday, 15 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Tuesday, 8 July)
• Re: ISSUE VARY: Proposed wording (Tuesday, 8 July)
• Re: ISSUE CONTENT-ENCODING: Proposed wording (Monday, 7 July)
• ISSUE VARY: Proposed wording (Thursday, 3 July)
• ISSUE PROXY-AUTHORIZATION: Proposal wording (Thursday, 3 July)
• ISSUE CONTENT-LOCATION: Proposed wording (Thursday, 3 July)
• ISSUE CONTENT-ENCODING: Proposed wording (Thursday, 3 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Tuesday, 1 July)

Henry Sanders (Exchange)

• RE: Head response Transfer-Encoding: chunked? (Thursday, 18 September)
• RE: Last-Modified in chunked footer (Wednesday, 3 September)

Hyoung-Kee Choi

• Proxy (Monday, 15 September)
• tcpdump (Friday, 5 September)
• tcpdump (Thursday, 21 August)

Internet-Drafts@ietf.org

• I-D ACTION:draft-ietf-http-uahint-01.txt (Wednesday, 17 September)
• I-D ACTION:draft-ietf-http-negotiation-04.txt (Tuesday, 16 September)
• I-D ACTION:draft-ietf-http-alternates-00.txt (Tuesday, 16 September)
• I-D ACTION:draft-ietf-http-req-sum-00.txt (Tuesday, 16 September)
• I-D ACTION:draft-ietf-http-options-02.txt (Wednesday, 3 September)
• I-D ACTION:draft-ietf-http-digest-aa-rev-00.txt (Tuesday, 5 August)
• I-D ACTION:draft-ietf-http-options-01.txt (Tuesday, 5 August)
• I-D ACTION:draft-ietf-http-state-man-mec-03.txt,.ps (Saturday, 2 August)
• I-D ACTION: draft-ietf-http-options-00.txt (Thursday, 31 July)
• I-D ACTION:draft-ietf-http-feature-reg-02.txt (Tuesday, 29 July)
• I-D ACTION:draft-ietf-http-feature-scenarios-01.txt (Tuesday, 29 July)
• I-D ACTION:draft-ietf-http-rvsa-v10-02.txt (Tuesday, 29 July)
• I-D ACTION:draft-ietf-http-negotiation-03.txt (re-send) (Monday, 28 July)
• I-D ACTION:draft-ietf-http-negotiation-03.txt (Monday, 28 July)
• I-D ACTION:draft-ietf-http-pep-04.txt, .ps (Wednesday, 16 July)
• I-D ACTION:draft-ietf-http-negotiate-scenario-01.txt (Wednesday, 16 July)
• I-D ACTION:draft-ietf-http-feature-scenarios-00.txt (Tuesday, 8 July)
• I-D ACTION:draft-ietf-http-feature-reg-01.txt (Tuesday, 8 July)
• I-D ACTION:draft-ietf-http-hit-metering-03.txt (Tuesday, 8 July)

Jacob Schroeder

• spec-08-EBNF analysis (Saturday, 2 August)

Jaye, Dan

• RE: comments on jaye-trust-state-01 (Friday, 12 September)
• RE: FW: revised trusted cookie spec (Thursday, 28 August)
• RE: FW: revised trusted cookie spec (Wednesday, 27 August)
• FW: revised trusted cookie spec (Thursday, 14 August)
• RE: can't really be LAST CALL,"HTTP State Management Mechanism (Rev1) " to Propo (Friday, 25 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Thursday, 17 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard (Thursday, 10 July)

Jeffrey Mogul

• Re: Content-Coding on POST (Thursday, 11 September)
• Re: Compressing HTML (Wednesday, 10 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: Spelling of "cachable" (Wednesday, 3 September)
• Spelling of "cachable" (Tuesday, 2 September)
• Re: 19.9 requirements summary (Thursday, 21 August)
• inconsistent use of MAY & SHOULD in 14.36.2 Range Retrieval Requests (Friday, 8 August)
• Re: draft-ieft-http-options-00.txt (Friday, 8 August)
• Re: Comments on OPTIONS draft (Friday, 8 August)
• Re: multipart/byteranges (Monday, 4 August)
• Re: multipart/byteranges (Monday, 4 August)
• Re: Implementation Experience Content Encoding (Friday, 1 August)
• Re: Issue 1310_CACHE (Thursday, 31 July)
• Re: Case (in)sensitivity in (Non-)Compliance headers (Wednesday, 30 July)
• Re: Updated proposal for OPTIONS issue (Wednesday, 30 July)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 30 July)
• Re: Updated proposal for CONTENT-ENCODING issue (Monday, 28 July)
• Updated proposal for OPTIONS issue (Friday, 25 July)
• Updated proposal for CONTENT-ENCODING issue (Friday, 25 July)
• Re: CONTENT-ENCODING: FIXED revised proposed wording (Thursday, 24 July)
• Proposed resolution for IDEMPOTENT issue (Thursday, 24 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Thursday, 24 July)
• Re: Another try at OPTIONS (Thursday, 24 July)
• Re: Another try at OPTIONS (Thursday, 24 July)
• Re: HTTP status codes (Wednesday, 23 July)
• Re: CONTENT-ENCODING: FIXED revised proposed wording (Wednesday, 23 July)
• CONTENT-ENCODING: FIXED revised proposed wording (Wednesday, 23 July)
• CONTENT-ENCODING: revised proposed wording (Wednesday, 23 July)
• Another try at OPTIONS (Tuesday, 22 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• Proposed solution for issue CLARIFY-NO-CACHE (Tuesday, 22 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Monday, 21 July)
• Any objections to "Accept-encoding: gzip, *;q=0"? (Monday, 21 July)
• RANGE-ERROR: proposed solution (Monday, 21 July)
• Re: ISSUE CACHE-DIRECTIVE: What is the proposal? (Monday, 21 July)
• LAST CALL on MAX-AGE issue (Saturday, 19 July)
• Revised resolution for the STATUS100 issue (Friday, 18 July)
• Re: Proposed resolution for the STATUS100 issue (Friday, 18 July)
• Re: STATUS100 Re: Proposed resolution (Friday, 18 July)
• Re: Proposed resolution for the STATUS100 issue (Thursday, 17 July)
• Re: STATUS100 Re: Proposed resolution (Thursday, 17 July)
• Re: Proposed resolution for the STATUS100 issue (Thursday, 17 July)
• Re: STATUS100 Re: Proposed resolution (Thursday, 17 July)
• Re: STATUS100 Re: Proposed resolution (Thursday, 17 July)
• Proposed resolution for the STATUS100 issue (Wednesday, 16 July)
• Re: Is 100-Continue hop-by-hop? (Thursday, 10 July)
• Re: ISSUE VARY: Proposed wording (Thursday, 10 July)
• Re: ISSUE VARY: Proposed wording (Wednesday, 9 July)
• Re: Is 100-Continue hop-by-hop? (Wednesday, 9 July)
• Summary of STATUS100 issue (Wednesday, 9 July)
• Re: HIT METERING to IESG on July 15 (Tuesday, 8 July)
• Re: HIT METERING to IESG on July 15 (Tuesday, 8 July)
• Is 100-Continue hop-by-hop? (Monday, 7 July)
• Interesting stats on the prevalence of bogus Last-Modified times (Friday, 4 July)
• Re: Proposal: 100-Continue optional under Client control (Wednesday, 2 July)
• Re: Proposal: 100-Continue optional under Client control (Wednesday, 2 July)

Jim Gettys

• Clock skew and the importance of clock synchronization in HTTP servers. (Friday, 12 September)
• DATE-IF-MODIFIED (Friday, 5 September)
• Re: Spelling of "cachable" (Wednesday, 3 September)
• Re: Basic Authentication behavior (Tuesday, 2 September)
• Re: Interoperability Event (Tuesday, 2 September)
• Re: 301/302 (Friday, 29 August)
• Re: 301/302 (Friday, 29 August)
• Draft 08 submitted to IETF ID editor. (Thursday, 31 July)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 30 July)
• Cutoff for Draft 08 of the HTTP/1.1 spec. (Wednesday, 30 July)
• New Editorial issue MESSAGE-BODY (Wednesday, 30 July)
• Issues-list item "CACHING-CGI" (Tuesday, 29 July)
• CACHING editorial issue... (Monday, 28 July)
• RE: New Issue REDIRECTS (Friday, 25 July)
• New Issue REDIRECTS (Friday, 25 July)
• Re: HTTP status codes (Wednesday, 23 July)
• Editorial ISSUE REMOVE_19.6 (Monday, 21 July)

Jim Whitehead

• RE: SSL Tunneling; Informational RFC; Last call? (Wednesday, 17 September)
• Re: Comments on OPTIONS draft (Thursday, 7 August)
• Comments on OPTIONS draft (Thursday, 7 August)
• Re: Editorial ISSUE REMOVE_19.6 (Tuesday, 22 July)

Joel N. Weber II

• Re: some thoughts on extensions on REQUEST line. (Wednesday, 24 September)
• Re: Clock skew and the importance of clock synchronization in HTTP servers. (Friday, 12 September)
• Re: Basic Authentication behavior (Friday, 5 September)
• Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Thursday, 24 July)
• Re: HTTP status codes (Wednesday, 23 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• Re: STATUS100 Re: Proposed resolution (Saturday, 19 July)
• Re: Proposal: 100-Continue optional under Client control (Friday, 4 July)

John C. Mallery

• Re: [URN] HTTP resolution protocol (Thursday, 17 July)

John Franks

• Re: 301/302 (Monday, 8 September)
• Re: Basic Authentication behavior (Monday, 8 September)
• Re: 301/302 (Monday, 8 September)
• Re: Basic Authentication behavior (Sunday, 7 September)
• Re: 301/302 (Friday, 5 September)
• Re: 301/302 (Friday, 5 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: 301/302 (Thursday, 4 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: Spelling of "cachable" (Wednesday, 3 September)
• Basic Authentication behavior (Tuesday, 2 September)
• Vary and server parsed documents (Saturday, 30 August)
• Re: RE-VERSION (Wednesday, 13 August)
• Re: RE-VERSION (Tuesday, 12 August)
• Re: RE-VERSION (Tuesday, 12 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Saturday, 9 August)
• Re: RE-VERSION (Friday, 8 August)
• Re: RE-VERSION (Friday, 8 August)
• Re: http-digest-aa-rev-00.txt (Wednesday, 6 August)
• Re: 301/302 (Friday, 1 August)
• Re: I-D on RFC 2069 issue: digest request (Thursday, 24 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)

John Seraphin

• RE: RE-VERSION (Sunday, 10 August)

Jonathan Stark

• Re: Removing CommentURL (Sunday, 27 July)
• Re: Removing CommentURL (Friday, 25 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Tuesday, 22 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Tuesday, 22 July)

Josh

• Re: Proxy (Monday, 15 September)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Tuesday, 1 July)

Josh Cohen

• Re: indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)
• (tangent) Re: 301/302 (Thursday, 4 September)
• RE-VERSION (Thursday, 4 September)
• Re: 301/302 (Thursday, 4 September)
• Re: 301/302 (Wednesday, 3 September)
• Re: 301/302 (Sunday, 31 August)
• Re: 301/302 (Friday, 29 August)
• RE-VERSION (Monday, 11 August)
• RE-VERSION (Friday, 8 August)
• Re: Feedback on: draft-cohen-http305306-02.txt (Wednesday, 30 July)
• Re: [Fwd: 301/302] (Tuesday, 29 July)
• [Fwd: 301/302] (Tuesday, 29 July)
• 305/306 spec (Friday, 25 July)
• Re: Another try at OPTIONS (Thursday, 24 July)
• SPEC 305/306 (Tuesday, 22 July)
• OPTIONS Spec (Tuesday, 22 July)
• Re: ISSUE CONTENT-ENCODING: Proposed wording (Saturday, 19 July)
• 305/306 (Thursday, 17 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)

Judson Valeski

• commentURL, again. (Monday, 18 August)
• Re: Removing CommentURL (Friday, 8 August)
• Re: Removing CommentURL (Sunday, 27 July)
• Re: Removing CommentURL (Saturday, 26 July)
• Re: Removing CommentURL (Friday, 25 July)
• Re: Removing CommentURL (Friday, 25 July)

Keld J|rn Simonsen

• cookies and security (Tuesday, 23 September)

Kevin J. Dyer

• Re: Using Content-Encoding and Content-Disposition together (Thursday, 7 August)

Klaus Weide

• Re: 301/302 (Friday, 5 September)
• extensibility of status codes (was: 301/302) (Friday, 5 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: 301/302 (Thursday, 4 September)
• Re: Last-Modified in chunked footer (Thursday, 4 September)
• Re: 301/302 (Thursday, 4 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: 301/302 (Wednesday, 3 September)
• RE: 301/302 (Wednesday, 3 September)
• Re: 301/302 (Friday, 29 August)
• Re: 301/302 (Friday, 29 August)
• What is a "message version" (was Re: RE-VERSION) (Tuesday, 12 August)
• Re: RE-VERSION (Tuesday, 12 August)
• Re: RE-VERSION (Tuesday, 12 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• "Warning" in draft -08 (Thursday, 7 August)
• Content-Disposition suggested text changes (Thursday, 7 August)
• Re: Using Content-Encoding and Content-Disposition together (Thursday, 7 August)
• Using Content-Encoding and Content-Disposition together (Saturday, 2 August)
• Re: The meaning of 301 (was Re: 301/302) (Wednesday, 30 July)
• Re: 301/302 (Wednesday, 30 July)
• The meaning of 301 (was Re: 301/302) (Wednesday, 30 July)

Koen Holtman

• Re: Interest in standard HTTP headers for specifying client (Friday, 19 September)
• Re: Head response Transfer-Encoding: chunked? (Thursday, 18 September)
• Re: Globally unique e-tags, if-match on content-ID, etc. (Monday, 15 September)
• Re: Clock skew and the importance of clock synchronization in HTTP servers. (Monday, 15 September)
• New content negotiation drafts available (Monday, 15 September)
• I-D ACTION:draft-holtman-http-safe-03.txt (fwd) (Friday, 12 September)
• Re: Comments on I-D ACTION:draft-ietf-http-options-02.txt (Tuesday, 9 September)
• Re: DATE-IF-MODIFIED (Tuesday, 9 September)
• Re: Last-Modified in chunked footer (Tuesday, 9 September)
• Re: 301/302 (Monday, 8 September)
• Re: Last-Modified in chunked footer (Monday, 8 September)
• Re: 301/302 (Monday, 8 September)
• Re: FW: revised trusted cookie spec (Monday, 8 September)
• Safe header -> experimental RFC (Monday, 8 September)
• Re: 301/302 (Wednesday, 3 September)
• Re: FW: revised trusted cookie spec (Tuesday, 2 September)
• Proposed Standard for Alternates header (Tuesday, 2 September)
• Re: Issue SAFE (Tuesday, 2 September)
• Re: 301/302 (Friday, 29 August)
• Re: 301/302 (Friday, 29 August)
• Re: draft-ieft-http-options-00.txt (Thursday, 7 August)
• Re: Using Content-Encoding and Content-Disposition together (Thursday, 7 August)
• Re: Using Content-Encoding and Content-Disposition together (Tuesday, 5 August)
• Re: HTTP-WG new charter milestones (Thursday, 31 July)
• Re: Issues-list item "CACHING-CGI" (Wednesday, 30 July)
• Re: 301/302 (Tuesday, 29 July)
• Re: Set-Cookie2: "additive" vs. "independent" (Tuesday, 29 July)
• Issue CONTENT-ENCODING (Monday, 28 July)
• New content negotiation drafts available (Monday, 28 July)
• Re: HTTP status codes (Thursday, 24 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Thursday, 24 July)
• Re: CONTENT-ENCODING: FIXED revised proposed wording (Thursday, 24 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Thursday, 24 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• Re: ISSUE: LANGUAGE-TAG (Monday, 21 July)
• Re: draft-ietf-http-feature-reg-01.txt (Saturday, 19 July)
• ISSUE CACHE-DIRECTIVE: What is the proposal? (Saturday, 19 July)
• ISSUE QUOTED-BACK: What is the proposal? (Saturday, 19 July)
• Re: New feature tag registration drafts available (Saturday, 19 July)
• Re: draft-ietf-http-negotiation-02.txt (Saturday, 19 July)
• Re: ISSUE: LANGUAGE-TAG (Saturday, 19 July)
• Re: STATUS100 Re: Proposed resolution (Friday, 18 July)
• Re: Proposed resolution for the STATUS100 issue (Friday, 18 July)
• Re: draft-ietf-http-feature-reg-01.txt (Monday, 14 July)
• Re: New feature tag registration drafts available (Monday, 14 July)
• Re: Content negotiation requirements (Monday, 14 July)
• Re: draft-ietf-http-negotiation-02.txt (Monday, 14 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Friday, 11 July)
• Re: Is 100-Continue hop-by-hop? (Friday, 11 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Friday, 11 July)
• Re: New feature tag registration drafts available (Thursday, 10 July)
• Re: Is 100-Continue hop-by-hop? (Thursday, 10 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Thursday, 10 July)
• Re: Summary of STATUS100 issue (Thursday, 10 July)
• Re: ISSUE VARY: Proposed wording (Thursday, 10 July)
• Re: ISSUE VARY: Proposed wording (Thursday, 10 July)
• Re: ISSUE CONTENT-ENCODING: Proposed wording (Wednesday, 9 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Wednesday, 9 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Wednesday, 9 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Tuesday, 8 July)
• Re: ISSUE CONTENT-LOCATION: Proposed wording (Tuesday, 8 July)
• Re: Refresh, non-standard headers, [was Re: Forcing to another page to load] (Tuesday, 8 July)
• New feature tag registration drafts available (Monday, 7 July)
• Re: ISSUE VARY: Proposed wording (Monday, 7 July)
• Re: SAFE, UAHINT and other things not part of HTTP/1.1 now (Monday, 7 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Friday, 4 July)
• Re: Proposal: 100-Continue optional under Client control (Friday, 4 July)
• Re: GET and referer security considerations (Friday, 4 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Friday, 4 July)
• Re: ISSUE CONTENT-ENCODING: Proposed wording (Friday, 4 July)
• Re: Revised HTTP WG charter dates (Friday, 4 July)
• Re: Content negotiation requirements (Friday, 4 July)
• Re: feature registration expired (Friday, 4 July)
• Re: GET and referer security considerations (Wednesday, 2 July)
• GET and referer security considerations (Tuesday, 1 July)

Larry Masinter

• Calculation of age headers (Saturday, 27 September)
• HTTP-WG recommends "SAFE" and "UAHINT" for "Experimental" (Friday, 26 September)
• Re: Weekly Internet HTTP/1.1 Tests (Wednesday, 24 September)
• Re: Interest in standard HTTP headers for specifying client (Friday, 19 September)
• Re: Interest in standard HTTP headers for specifying client display attributes? (Thursday, 18 September)
• [Fwd: I-D ACTION:draft-lyon-itp-nodes-02.txt] (Wednesday, 17 September)
• Re: SSL Tunneling; Informational RFC; Last call? (Tuesday, 16 September)
• Age calculation in HTTP: two Internet Drafts (Tuesday, 16 September)
• Re: Last-Modified in chunked footer (Tuesday, 16 September)
• indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)
• Re: Last-Modified in chunked footer (Monday, 15 September)
• Re: Last-Modified in chunked footer (Saturday, 13 September)
• Globally unique e-tags, if-match on content-ID, etc. (Saturday, 13 September)
• Revised http://www.w3.org/Protocols/HTTP/Issues/ (Thursday, 11 September)
• Re: Content-Coding on POST (Thursday, 11 September)
• Re: Compressing HTML (Thursday, 11 September)
• Alternates? (Thursday, 4 September)
• Re: Last-Modified in chunked footer (Thursday, 4 September)
• (revised) Minutes, HTTP Working Group, Munich IETF Aug 11-12 (Thursday, 4 September)
• Re: 301/302 (Wednesday, 3 September)
• Re: FW: revised trusted cookie spec (Wednesday, 3 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: 301/302 (Wednesday, 3 September)
• [Fwd: RFC 2183 on Content-Disposition] (Wednesday, 3 September)
• DRAFT Minutes, HTTP Working Group, Munich IETF (Sunday, 31 August)
• Re: Interoperability Event (Saturday, 30 August)
• Re: Interoperability Event (Friday, 29 August)
• Re: FW: revised trusted cookie spec (Thursday, 28 August)
• Re: 19.9 requirements summary (Friday, 22 August)
• Re: FW: revised trusted cookie spec (Tuesday, 19 August)
• Re: FW: revised trusted cookie spec (Tuesday, 19 August)
• Re: commentURL, again. (Monday, 18 August)
• Re: FW: revised trusted cookie spec (Monday, 18 August)
• Re: FW: revised trusted cookie spec (Monday, 18 August)
• "virtual connect-a-thon" (Monday, 18 August)
• Short report, HTTP WG meeting (Friday, 15 August)
• Re: Q: Methods and Headers? (Wednesday, 13 August)
• Re: Revised Agenda for Munich (Saturday, 9 August)
• Revised Agenda for Munich (Saturday, 9 August)
• Re: Comments on OPTIONS draft (Friday, 8 August)
• Re: Using Content-Encoding and Content-Disposition together (Thursday, 7 August)
• Re: http-digest-aa-rev-00.txt (Thursday, 7 August)
• Re: Agenda for Munich (Wednesday, 6 August)
• Agenda for Munich (Wednesday, 6 August)
• Re: agenda for Munich (Friday, 1 August)
• agenda for Munich (Friday, 1 August)
• Re: 301/302 (Friday, 1 August)
• Re: 301/302 (Thursday, 31 July)
• HTTP-WG new charter milestones (Thursday, 31 July)
• Re: 301/302 (Thursday, 31 July)
• Re: 301/302 (Wednesday, 30 July)
• Re: 301/302 (Tuesday, 29 July)
• IETF in Munich: 8/11 & 8/12 (Tuesday, 29 July)
• LAST CALLs, closed issues, and new HTTP/1.1 draft (Monday, 28 July)
• Removing CommentURL (Friday, 25 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Thursday, 24 July)
• Additional LAST CALL issues (Thursday, 24 July)
• can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Wednesday, 23 July)
• Re: Roy Fielding's comments on draft-ietf-http-hit-metering-03 (Tuesday, 22 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• Re: STATUS100 Re: Proposed resolution (Saturday, 19 July)
• Re: ISSUE: LANGUAGE-TAG (Friday, 18 July)
• LAST CALL (and other status changes) on HTTP/1.1 issues (Wednesday, 16 July)
• Request IESG action for draft-ietf-http-hit-metering-03.txt (Wednesday, 16 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard (Thursday, 10 July)
• MUST and SHOULD, other kinds of proxies, and ISSUE PROXY-AUTHORIZATION (Thursday, 10 July)
• HIT METERING to IESG on July 15 (Tuesday, 8 July)
• Re-revised HTTP WG charter dates (Tuesday, 8 July)
• LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard (Tuesday, 8 July)
• Refresh, non-standard headers, [was Re: Forcing to another page to load] (Monday, 7 July)
• SAFE, UAHINT and other things not part of HTTP/1.1 now (Sunday, 6 July)
• feature registration expired (Thursday, 3 July)
• LAST CALL on four issues from http://www.w3.org/pub/WWW/Protocols/HTTP/Issues/ (Thursday, 3 July)
• Revised HTTP WG charter dates (Thursday, 3 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: GET and referer security considerations (Tuesday, 1 July)

Laurent Douillet

• HTTP POST and Cookies (Tuesday, 2 September)

Lou Montulli

• Re: 301/302 (Friday, 29 August)

Marc Slemko

• Re: indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)

Mark D. Wood

• Interest in standard HTTP headers for specifying client display attributes? (Wednesday, 17 September)

Martin Hamilton

• cache-busting doc as RFC ? (Wednesday, 16 July)

Martin J Duerst

• Three new I-Ds re. URL i18n (Thursday, 31 July)

Martin J. Duerst

• Re: Agenda for Munich (Wednesday, 6 August)
• ISSUE: CHARSET DEFAULT (Monday, 28 July)
• Re: CONTENT-ENCODING: FIXED revised proposed wording (Wednesday, 23 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Wednesday, 23 July)
• Re: ISSUE: LANGUAGE-TAG (Monday, 21 July)
• ISSUE: LANGUAGE-TAG (Friday, 18 July)

Martin J. Dürst

• Re: some thoughts on extensions on REQUEST line. (Wednesday, 24 September)

Matthew Rubenstein

• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard (Friday, 11 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard (Thursday, 10 July)
• Re: GET and referer security considerations (Wednesday, 2 July)

Maurizio Codogno

• Re: Last-Modified in chunked footer (Friday, 5 September)
• Updated proposal for CONTENT-ENCODING issue (Monday, 28 July)
• Re: Removing CommentURL (Monday, 28 July)
• HTTP status codes (resent) (Monday, 28 July)
• Re: Proposed resolution for the STATUS100 issue (Thursday, 17 July)
• Re: ISSUE VARY: Proposed wording (Monday, 7 July)

Misha Wolf

• Eleventh International Unicode Conference (Wednesday, 9 July)

Mitch Wyle

• web login session transfer? (Wednesday, 3 September)

Neal McBurnett

• input on HTTP for the year 2000 working group (Tuesday, 15 July)

Nick Barrett

• POST (Saturday, 24 August)

Nirmal Patil

• multipart/x-mixed-replace (Wednesday, 30 July)

Patrick McManus

• req-sum-00 (Monday, 22 September)
• 19.9 requirements summary (Thursday, 21 August)
• Re: Using Content-Encoding and Content-Disposition together (Saturday, 2 August)
• Re: Implementation Experience Content Encoding (Friday, 1 August)
• Re: Implementation Experience Content Encoding (Friday, 1 August)
• Re: Implementation Experience Content Encoding (Friday, 1 August)
• Implementation Experience Content Encoding (Friday, 1 August)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• Re: GET and referer security considerations (Thursday, 3 July)

Paul Leach

• RE: Issue 1310_CACHE (Thursday, 31 July)

Phillip Hallam-Baker

• RE: indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)
• RE: indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)
• RE: Globally unique e-tags, if-match on content-ID, etc. (Monday, 15 September)

Phillip M. Hallam-Baker

• Re: Updated proposal for CONTENT-ENCODING issue (Friday, 25 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Monday, 21 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Tuesday, 8 July)
• Re: Digest Authentication bleat (Tuesday, 1 July)

Pixieo2@aol.com

• Re: Proposed resolution for the STATUS100 issue (Friday, 18 July)

Ralph-W koerner

• cc:Mail Link to SMTP Undeliverable Message (Friday, 11 July)

rlgray@raleigh.ibm.com

• Re: Head response Transfer-Encoding: chunked? (Thursday, 18 September)
• RE: Last-Modified in chunked footer (Tuesday, 16 September)
• Re: SSL Tunneling; Informational RFC; Last call? (Tuesday, 16 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Last-Modified in chunked footer (Wednesday, 3 September)
• PUT multipart (Friday, 22 August)
• Re: agenda for Munich (Monday, 4 August)
• Re: Updated proposal for OPTIONS issue (Tuesday, 29 July)
• Re: STATUS100 Re: Proposed resolution (Thursday, 17 July)
• Re: Summary of STATUS100 issue (Thursday, 17 July)
• STATUS100 Re: Proposed resolution (Thursday, 17 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Thursday, 10 July)

Rob

• Re: Forcing to another page to load (Monday, 7 July)

Ron Daniel, Jr.

• Re: [URN] HTTP resolution protocol (Thursday, 17 July)

Ross Patterson

• Re: some thoughts on extensions on REQUEST line. (Wednesday, 24 September)
• Re: Age calculation in HTTP: two Internet Drafts (Tuesday, 23 September)
• Re: I-D ACTION:draft-ietf-http-req-sum-00.txt (Friday, 19 September)
• Re: SSL Tunneling; Informational RFC; Last call? (Monday, 15 September)
• Re: DATE-IF-MODIFIED (Monday, 8 September)
• Re: http-digest-aa-rev-00.txt (Thursday, 7 August)
• Re: http-digest-aa-rev-00.txt (Thursday, 7 August)
• Re: Updated proposal for OPTIONS issue (Wednesday, 30 July)
• Re: Updated proposal for OPTIONS issue (Wednesday, 30 July)
• Case (in)sensitivity in (Non-)Compliance headers (Wednesday, 30 July)
• Re: 305/306 (Monday, 21 July)
• Re: Refresh, non-standard headers (Tuesday, 8 July)
• Re: GET and referer security considerations (Wednesday, 2 July)

Roy T. Fielding

• Re: Age calculation in HTTP: two Internet Drafts (Friday, 26 September)
• Re: SSL Tunneling; Informational RFC; Last call? (Saturday, 20 September)
• Re: SSL Tunneling; Informational RFC; Last call? (Wednesday, 17 September)
• Re: Clock skew and the importance of clock synchronization in HTTP servers. (Friday, 12 September)
• Re: 301/302 (Monday, 8 September)
• Re: Basic Authentication behavior (Monday, 8 September)
• Re: 301/302 (Friday, 5 September)
• Re: 301/302 (Friday, 5 September)
• Re: 301/302 (Friday, 5 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: Last-Modified in chunked footer (Thursday, 4 September)
• Re: RE-VERSION (Thursday, 4 September)
• Re: 301/302 (Thursday, 4 September)
• Re: 301/302 (Saturday, 30 August)
• Re: 301/302 (Friday, 29 August)
• Re: RE-VERSION (Wednesday, 13 August)
• Re: RE-VERSION (Wednesday, 13 August)
• Re: RE-VERSION (Wednesday, 13 August)
• Re: RE-VERSION (Tuesday, 12 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Monday, 11 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Saturday, 9 August)
• Re: RE-VERSION (Saturday, 9 August)
• response w/o content-length (Saturday, 9 August)
• Re: Issues-list item "CACHING-CGI" (Saturday, 9 August)
• Re: New Editorial issue MESSAGE-BODY (Saturday, 9 August)
• Re: 301/302 (Tuesday, 29 July)
• Re: Issues-list item "CACHING-CGI" (Tuesday, 29 July)
• Re: 301/302 (Tuesday, 29 July)
• Re: 301/302 (Sunday, 27 July)
• Re: Redirects (Sunday, 27 July)
• Re: OPTIONS Spec (Sunday, 27 July)
• Re: New Issue REDIRECTS (Friday, 25 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Thursday, 24 July)
• Re: LAST CALL on MAX-AGE issue (Saturday, 19 July)
• Re: ISSUE VARY: Proposed wording (Friday, 18 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Friday, 18 July)
• Re: STATUS100 Re: Proposed resolution (Friday, 18 July)
• Re: Proposed resolution for the STATUS100 issue (Friday, 18 July)
• draft-ietf-http-hit-metering-03.txt (Thursday, 17 July)
• Re: Is 100-Continue hop-by-hop? (Saturday, 12 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard (Thursday, 10 July)
• Re: ISSUE PROXY-AUTHORIZATION: Proposal wording (Wednesday, 9 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Wednesday, 2 July)
• Re: HTTP/1.1 & Proxies (Tuesday, 1 July)

Sanjath

• some thoughts on extensions on REQUEST line. (Wednesday, 24 September)

Scott Lawrence

• Weekly Internet HTTP/1.1 Tests (Wednesday, 24 September)
• Proposal for Weekly Internet HTTP/1.1 Tests (Monday, 22 September)
• Interoperability Test Survey (updated) (Monday, 22 September)
• Re: draft-ietf-http-req-sum-00.txt (Thursday, 18 September)
• Re: Age calculation in HTTP: two Internet Drafts (Thursday, 18 September)
• Re: Interest in standard HTTP headers for specifying client display attributes? (Thursday, 18 September)
• Interoperability Test Survey (Wednesday, 17 September)
• Re: Head response Transfer-Encoding: chunked? (Wednesday, 17 September)
• Head response Transfer-Encoding: chunked? (Monday, 15 September)
• Re: Last-Modified in chunked footer (Monday, 15 September)
• Re: Last-Modified in chunked footer (Monday, 15 September)
• Re: Last-Modified in chunked footer (Monday, 8 September)
• Re: DATE-IF-MODIFIED (Monday, 8 September)
• Re: Basic Authentication behavior (Monday, 8 September)
• Re: 301/302 (Friday, 5 September)
• Re: Last-Modified in chunked footer (Friday, 5 September)
• Re: 301/302 (Thursday, 4 September)
• Re: RE-VERSION (Thursday, 4 September)
• Re: 301/302 (Thursday, 4 September)
• Re: 301/302 (Wednesday, 3 September)
• Re: 301/302 (Wednesday, 3 September)
• Re: Last-Modified in chunked footer (Wednesday, 3 September)
• Re: Basic Authentication behavior (Tuesday, 2 September)
• Re: Interoperability Event (Friday, 29 August)
• Re: Interoperability Event (Friday, 29 August)
• Re: Interoperability Event (Friday, 29 August)
• Interoperability Event (Friday, 29 August)
• Re: RE-VERSION (Tuesday, 12 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: RE-VERSION (Sunday, 10 August)
• Re: Implementation Experience Content Encoding (Friday, 1 August)
• Re: Implementation Experience Content Encoding (Friday, 1 August)
• Re: agenda for Munich (Friday, 1 August)
• AUTH-CHUNKED proposed resolution (Monday, 28 July)
• Re: Updated proposal for OPTIONS issue (Friday, 25 July)
• Re: Another try at OPTIONS (Thursday, 24 July)
• Re: Another try at OPTIONS (Thursday, 24 July)
• Re: Another try at OPTIONS (Wednesday, 23 July)
• 1.1 proxies? (Wednesday, 23 July)
• Re: OPTIONS Spec (Tuesday, 22 July)
• I-D on RFC 2069 issue: digest request (Tuesday, 22 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• Re: Any objections to "Accept-encoding: gzip, *;q=0"? (Tuesday, 22 July)
• STATUS100 Re: Proposed resolution (Thursday, 17 July)
• Re: Proposal: 100-Continue optional under Client control (Wednesday, 2 July)
• Re: GET and referer security considerations (Wednesday, 2 July)
• Re: GET and referer security considerations (Tuesday, 1 July)

Shel Kaphan

• Re: a positive "no thanks" to cookies? (Monday, 11 August)
• Re: a positive "no thanks" to cookies? (Monday, 11 August)
• a positive "no thanks" to cookies? (Sunday, 10 August)

Siew Sim

• Re: GET and referer security considerations (Wednesday, 2 July)

Steve Colby

• The significance of Cookies (Wednesday, 23 July)

Ted Hardie

• Re: Comment-URL question (Monday, 28 July)
• Re: Comment-URL question (Monday, 28 July)
• Comment-URL question (Monday, 28 July)
• Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Friday, 11 July)

The IESG

• Last Call: Simple Hit-Metering and Usage-Limiting for HTTP to Proposed Standard (Monday, 21 July)

touch@isi.edu

• RE: indefinite server-push (was 'Last-Modified in chunked footer') (Monday, 15 September)
• Re: a positive "no thanks" to cookies? (Monday, 11 August)
• Re: The significance of Cookies (Wednesday, 23 July)
• Re: Refresh, non-standard headers, [was Re: Forcing to another page to load] (Tuesday, 8 July)

Turner Rentz, III

• Re: Interoperability Event (Friday, 29 August)

Warren P. Chi

• Re: Forcing to another page to load (Sunday, 6 July)

Wingard, Steve

• RE: [Fwd: 301/302] (Tuesday, 29 July)

Woodhouse, Gregory

• RE: draft-ietf-http-req-sum-00.txt (Thursday, 18 September)
• RE: 301/302 (Saturday, 6 September)

Yaron Goland

• RE: Last-Modified in chunked footer (Wednesday, 17 September)
• RE: Last-Modified in chunked footer (Tuesday, 16 September)
• RE: Last-Modified in chunked footer (Monday, 15 September)
• RE: indefinite server-push (was 'Last-Modified in chunked footer' ) (Monday, 15 September)
• RE: Last-Modified in chunked footer (Monday, 15 September)
• RE: Globally unique e-tags, if-match on content-ID, etc. (Monday, 15 September)
• RE: Comments on I-D ACTION:draft-ietf-http-options-02.txt (Wednesday, 10 September)
• Comments on I-D ACTION:draft-ietf-http-options-02.txt (Tuesday, 9 September)
• RE: Last-Modified in chunked footer (Monday, 8 September)
• RE: Last-Modified in chunked footer (Sunday, 7 September)
• RE: Last-Modified in chunked footer (Sunday, 7 September)
• RE: 301/302 (Thursday, 4 September)
• RE: 301/302 (Wednesday, 3 September)
• RE: 301/302 (Wednesday, 3 September)
• RE: 301/302 (Wednesday, 3 September)
• RE: State Management pre-draft - combinational requirement (Thursday, 7 August)
• RE: Using Content-Encoding and Content-Disposition together (Tuesday, 5 August)
• RE: multipart/byteranges (Tuesday, 5 August)
• RE: multipart/byteranges (Monday, 4 August)
• multipart/byteranges (Monday, 4 August)
• RE: 301/302 (Thursday, 31 July)
• RE: 301/302 (Thursday, 31 July)
• RE: 301/302 (Tuesday, 29 July)
• RE: 301/302 (Monday, 28 July)
• RE: 301/302 (Friday, 25 July)
• 301/302 (Friday, 25 July)
• RE: New Issue REDIRECTS (Friday, 25 July)
• RE: New Issue REDIRECTS (Friday, 25 July)
• RE: Proposed resolution for the STATUS100 issue (Friday, 18 July)
• RE: Proposed resolution for the STATUS100 issue (Thursday, 17 July)
• RE: Is 100-Continue hop-by-hop? (Thursday, 17 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Friday, 11 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Friday, 11 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard (Friday, 11 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard (Friday, 11 July)
• RE: Is 100-Continue hop-by-hop? (Friday, 11 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo (Friday, 11 July)
• RE: Is 100-Continue hop-by-hop? (Thursday, 10 July)
• RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard (Wednesday, 9 July)
• RE: HTTP/1.1 & Proxies (Tuesday, 1 July)

Yehuda Shiran

• POST problem (Thursday, 31 July)

Last message date: Saturday, 27 September 1997 23:00:34 UTC