W3C home
>
Mailing lists
>
Public
>
ietf-http-wg-old@w3.org
>
May to August 1997
ietf-http-wg-old@w3.org from May to August 1997 by date
1034 messages
:
Starting
Thursday, 1 May 1997 08:45:19 EDT,
Ending
Saturday, 30 August 1997 23:20:27 EDT
sort by
: [
thread
] [
author
] [ date ] [
subject
] [
attachment
]
Mail actions
: [
mail a new topic
]
Help
: [
How to use the archives
] [
Search in the archives
]
Sunday, 31 August
DRAFT Minutes, HTTP Working Group, Munich IETF
Larry Masinter
Saturday, 30 August
Re: 301/302
Josh Cohen
Re: 301/302
Foteos Macrides
Re: 301/302
Roy T. Fielding
Vary and server parsed documents
John Franks
Re: Interoperability Event
Larry Masinter
Friday, 29 August
Re: 301/302
Foteos Macrides
Re: 301/302
Klaus Weide
Re: Interoperability Event
Scott Lawrence
Re: 301/302
Koen Holtman
Re: Interoperability Event
Scott Lawrence
Re: 301/302
Koen Holtman
Re: Interoperability Event
Larry Masinter
Re: Interoperability Event
Scott Lawrence
Re: Interoperability Event
Turner Rentz, III
Re: 301/302
Jim Gettys
Re: 301/302
Jim Gettys
Interoperability Event
Scott Lawrence
Re: 301/302
Foteos Macrides
Re: 301/302
Roy T. Fielding
Thursday, 28 August
Re: 301/302
Klaus Weide
Re: 301/302
Josh Cohen
Re: 301/302
David W. Morris
Re: 301/302
Lou Montulli
RE: FW: revised trusted cookie spec
Jaye, Dan
Re: FW: revised trusted cookie spec
Larry Masinter
Tuesday, 26 August
RE: FW: revised trusted cookie spec
Jaye, Dan
Friday, 22 August
PUT multipart
rlgray@raleigh.ibm.com
Thursday, 21 August
Re: 19.9 requirements summary
Larry Masinter
Re: 19.9 requirements summary
Jeffrey Mogul
19.9 requirements summary
Patrick McManus
tcpdump
Hyoung-Kee Choi
Tuesday, 19 August
comments on jaye-trust-state-01
Dave Kristol
Re: FW: revised trusted cookie spec
hedlund
Re: FW: revised trusted cookie spec
Larry Masinter
Re: FW: revised trusted cookie spec
Foteos Macrides
RE: FW: revised trusted cookie spec
Fisher Mark
Re: FW: revised trusted cookie spec
Foteos Macrides
Re: FW: revised trusted cookie spec
Larry Masinter
Monday, 18 August
Re: FW: revised trusted cookie spec
Foteos Macrides
Re: commentURL, again.
Larry Masinter
Re: FW: revised trusted cookie spec
Larry Masinter
commentURL, again.
Judson Valeski
Re: FW: revised trusted cookie spec
Foteos Macrides
Re: FW: revised trusted cookie spec
Larry Masinter
"virtual connect-a-thon"
Larry Masinter
Friday, 15 August
Short report, HTTP WG meeting
Larry Masinter
Wednesday, 13 August
FW: revised trusted cookie spec
Jaye, Dan
Re: Q: Methods and Headers?
Larry Masinter
Re: RE-VERSION
John Franks
Tuesday, 12 August
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Roy T. Fielding
What is a "message version" (was Re: RE-VERSION)
Klaus Weide
Re: RE-VERSION
John Franks
Re: RE-VERSION
John Franks
Monday, 11 August
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Scott Lawrence
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
John Franks
Q: Methods and Headers?
Andreas Brusinsky
Re: RE-VERSION
John Franks
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Foteos Macrides
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Foteos Macrides
Re: RE-VERSION
John Franks
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
John Franks
Re: RE-VERSION
John Franks
Re: RE-VERSION
Foteos Macrides
Re: a positive "no thanks" to cookies?
Shel Kaphan
Re: RE-VERSION
Josh
Re: a positive "no thanks" to cookies?
touch@isi.edu
Re: RE-VERSION
John Franks
Re: RE-VERSION
John Franks
Re: RE-VERSION
Foteos Macrides
Re: RE-VERSION
Josh
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Josh
Re: a positive "no thanks" to cookies?
Benjamin Franz
Re: a positive "no thanks" to cookies?
Ben Laurie
Re: a positive "no thanks" to cookies?
David W. Morris
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Roy T. Fielding
Sunday, 10 August
Re: draft-ieft-http-options-00.txt
Dave Kristol
RE-VERSION
Josh Cohen
Re: RE-VERSION
Foteos Macrides
Re: a positive "no thanks" to cookies?
Shel Kaphan
Re: RE-VERSION
Josh
Re: a positive "no thanks" to cookies?
hedlund
Re: RE-VERSION
John Franks
a positive "no thanks" to cookies?
Shel Kaphan
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Ben Laurie
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
Foteos Macrides
Re: RE-VERSION
Klaus Weide
Re: RE-VERSION
John Franks
Re: RE-VERSION
John Franks
Re: RE-VERSION
John Franks
Re: RE-VERSION
Scott Lawrence
Re: RE-VERSION
Scott Lawrence
Re: RE-VERSION
Klaus Weide
RE: RE-VERSION
John Seraphin
Re: RE-VERSION
Roy T. Fielding
Saturday, 9 August
Re: RE-VERSION
Scott Lawrence
Re: RE-VERSION
David W. Morris
Re: RE-VERSION
John Franks
Re: Revised Agenda for Munich
Larry Masinter
Revised Agenda for Munich
Larry Masinter
Re: RE-VERSION
Roy T. Fielding
Re: RE-VERSION
Roy T. Fielding
response w/o content-length
Roy T. Fielding
Re: Issues-list item "CACHING-CGI"
Roy T. Fielding
Re: New Editorial issue MESSAGE-BODY
Roy T. Fielding
Friday, 8 August
inconsistent use of MAY & SHOULD in 14.36.2 Range Retrieval Requests
Jeffrey Mogul
Re: draft-ieft-http-options-00.txt
Jeffrey Mogul
Re: Comments on OPTIONS draft
Jeffrey Mogul
Re: RE-VERSION
John Franks
Re: Comments on OPTIONS draft
Larry Masinter
Q:Which headers go with which Methods?
Andreas Brusinsky
Re: RE-VERSION
John Franks
Re: RE-VERSION
David W. Morris
Re: Removing CommentURL
Judson Valeski
RE-VERSION
Josh Cohen
Thursday, 7 August
RE: State Management pre-draft - combinational requirement
Yaron Goland
"Warning" in draft -08
Klaus Weide
Re: draft-ieft-http-options-00.txt
Koen Holtman
draft-ieft-http-options-00.txt
Dave Kristol
Re: Comments on OPTIONS draft
Jim Whitehead
Re: Using Content-Encoding and Content-Disposition together
Koen Holtman
Comments on OPTIONS draft
Jim Whitehead
Content-Disposition suggested text changes
Klaus Weide
Re: http-digest-aa-rev-00.txt
David Jablon
Re: Using Content-Encoding and Content-Disposition together
Foteos Macrides
Re: Using Content-Encoding and Content-Disposition together
Kevin J. Dyer
Administriva: http-wg mailing list and spammers
Andy Norman
Re: Using Content-Encoding and Content-Disposition together
Klaus Weide
Wednesday, 6 August
Re: Using Content-Encoding and Content-Disposition together
Larry Masinter
Re: Using Content-Encoding and Content-Disposition together
Foteos Macrides
Re: http-digest-aa-rev-00.txt
Ross Patterson
Re: http-digest-aa-rev-00.txt
Ross Patterson
Re: http-digest-aa-rev-00.txt
Larry Masinter
Re: Using Content-Encoding and Content-Disposition together
Foteos Macrides
Re: http-digest-aa-rev-00.txt
David Jablon
Re: http-digest-aa-rev-00.txt
David Jablon
Re: Agenda for Munich
Larry Masinter
Re: http-digest-aa-rev-00.txt
John Franks
Re: Agenda for Munich
Martin J. Duerst
Re: http-digest-aa-rev-00.txt
David Jablon
Agenda for Munich
Larry Masinter
Tuesday, 5 August
I-D ACTION:draft-ietf-http-digest-aa-rev-00.txt
Internet-Drafts@ietf.org
Re: Using Content-Encoding and Content-Disposition together
Koen Holtman
I-D ACTION:draft-ietf-http-options-01.txt
Internet-Drafts@ietf.org
Monday, 4 August
RE: multipart/byteranges
David W. Morris
RE: Using Content-Encoding and Content-Disposition together
David W. Morris
RE: Using Content-Encoding and Content-Disposition together
Yaron Goland
RE: multipart/byteranges
Yaron Goland
Re: multipart/byteranges
Jeffrey Mogul
RE: multipart/byteranges
Yaron Goland
Re: multipart/byteranges
David W. Morris
Re: agenda for Munich
rlgray@raleigh.ibm.com
Re: multipart/byteranges
Jeffrey Mogul
Sunday, 3 August
multipart/byteranges
Yaron Goland
Saturday, 2 August
Re: Using Content-Encoding and Content-Disposition together
Patrick McManus
I-D ACTION:draft-ietf-http-state-man-mec-03.txt,.ps
Internet-Drafts@ietf.org
spec-08-EBNF analysis
Jacob Schroeder
Using Content-Encoding and Content-Disposition together
Klaus Weide
Friday, 1 August
Re: agenda for Munich
David W. Morris
Re: agenda for Munich
Larry Masinter
Re: Implementation Experience Content Encoding
Jeffrey Mogul
Re: Implementation Experience Content Encoding
Patrick McManus
Re: Implementation Experience Content Encoding
Scott Lawrence
Re: 301/302
David W. Morris
Re: Implementation Experience Content Encoding
Patrick McManus
Re: Implementation Experience Content Encoding
Scott Lawrence
Re: Implementation Experience Content Encoding
Patrick McManus
Re: 301/302
Ben Laurie
Implementation Experience Content Encoding
Patrick McManus
Re: agenda for Munich
Scott Lawrence
agenda for Munich
Larry Masinter
Re: 301/302
Foteos Macrides
Re: 301/302
John Franks
Re: 301/302
Ben Laurie
Re: 301/302
Larry Masinter
Thursday, 31 July
Re: Issue 1310_CACHE
Jeffrey Mogul
Re: 301/302
Larry Masinter
RE: 301/302
Yaron Goland
RE: 301/302
Yaron Goland
Re: 301/302
Ben Laurie
Re: HTTP-WG new charter milestones
Alfred Brock
Re: HTTP-WG new charter milestones
Koen Holtman
Draft 08 submitted to IETF ID editor.
Jim Gettys
Re: HTTP-WG new charter milestones
Foteos Macrides
I-D ACTION: draft-ietf-http-options-00.txt
Internet-Drafts@ietf.org
HTTP-WG new charter milestones
Larry Masinter
Re: 301/302
Larry Masinter
Three new I-Ds re. URL i18n
Martin J Duerst
POST problem
Yehuda Shiran
Wednesday, 30 July
RE: Issue 1310_CACHE
Paul Leach
multipart/x-mixed-replace
Nirmal Patil
Re: The meaning of 301 (was Re: 301/302)
Klaus Weide
Issue 1310_CACHE
Henrik Frystyk Nielsen
ISSUE: 403vs404
Henrik Frystyk Nielsen
Re: Updated proposal for OPTIONS issue
Ross Patterson
Re: Case (in)sensitivity in (Non-)Compliance headers
Jeffrey Mogul
Re: Updated proposal for OPTIONS issue
Jeffrey Mogul
Re: Issues-list item "CACHING-CGI"
Jim Gettys
Re: 301/302
Foteos Macrides
Re: The meaning of 301 (was Re: 301/302)
Foteos Macrides
Re: ISSUE VARY: Proposed wording
Henrik Frystyk Nielsen
Re: ISSUE VARY: Proposed wording
Henrik Frystyk Nielsen
Re: Issues-list item "CACHING-CGI"
Jeffrey Mogul
RE: 301/302
Arthur Bierer
Re: Issues-list item "CACHING-CGI"
Koen Holtman
Re: 301/302
Ben Laurie
Re: 301/302
Klaus Weide
Re: Updated proposal for OPTIONS issue
Ross Patterson
Re: Another try at OPTIONS
Henrik Frystyk Nielsen
The meaning of 301 (was Re: 301/302)
Klaus Weide
Re: 301/302
David W. Morris
Case (in)sensitivity in (Non-)Compliance headers
Ross Patterson
Re: New Editorial issue MESSAGE-BODY
David W. Morris
Re: 301/302
Larry Masinter
Cutoff for Draft 08 of the HTTP/1.1 spec.
Jim Gettys
New Editorial issue MESSAGE-BODY
Jim Gettys
Re: 301/302
Ben Laurie
Re: Issues-list item "CACHING-CGI"
David W. Morris
Re: Set-Cookie2: "additive" vs. "independent"
David W. Morris
Re: [Fwd: 301/302]
David W. Morris
Tuesday, 29 July
Re: Feedback on: draft-cohen-http305306-02.txt
Josh Cohen
Re: 301/302
Roy T. Fielding
Re: 301/302
Foteos Macrides
Re: Issues-list item "CACHING-CGI"
Roy T. Fielding
Re: 301/302
Roy T. Fielding
Re: Set-Cookie2: "additive" vs. "independent"
Dave Kristol
Re: Set-Cookie2: "additive" vs. "independent"
Dave Kristol
Re: [Fwd: 301/302]
Dave Kristol
Re: [Fwd: 301/302]
Josh Cohen
RE: [Fwd: 301/302]
Wingard, Steve
Re: [Fwd: 301/302]
Dave Kristol
[Fwd: 301/302]
Josh Cohen
Re: 301/302
Foteos Macrides
Issues-list item "CACHING-CGI"
Jim Gettys
Re: 301/302
Koen Holtman
RE: 301/302
Yaron Goland
Re: Set-Cookie2: "additive" vs. "independent"
Foteos Macrides
Re: Set-Cookie2: "additive" vs. "independent"
Foteos Macrides
Re: Set-Cookie2: "additive" vs. "independent"
Koen Holtman
Re: Set-Cookie2: "additive" vs. "independent"
David W. Morris
Re: Set-Cookie2: "additive" vs. "independent"
David W. Morris
Re: Updated proposal for OPTIONS issue
rlgray@raleigh.ibm.com
Re: an (unofficial) cookie draft
Dave Kristol
I-D ACTION:draft-ietf-http-feature-reg-02.txt
Internet-Drafts@ietf.org
I-D ACTION:draft-ietf-http-feature-scenarios-01.txt
Internet-Drafts@ietf.org
I-D ACTION:draft-ietf-http-rvsa-v10-02.txt
Internet-Drafts@ietf.org
Set-Cookie2: "additive" vs. "independent"
Dave Kristol
Re: 301/302
Larry Masinter
IETF in Munich: 8/11 & 8/12
Larry Masinter
Re: an (unofficial) cookie draft
David W. Morris
Re: Comment-URL question
David W. Morris
Monday, 28 July
Re: Comment-URL question
Ted Hardie
RE: 301/302
Yaron Goland
Re: Comment-URL question
Dave Kristol
Re: Comment-URL question
Ted Hardie
I-D ACTION:draft-ietf-http-negotiation-03.txt (re-send)
Internet-Drafts@ietf.org
Re: Comment-URL question
David W. Morris
Issue CONTENT-ENCODING
Koen Holtman
AUTH-CHUNKED proposed resolution
Scott Lawrence
New content negotiation drafts available
Koen Holtman
Re: Comment-URL question
Dave Kristol
Comment-URL question
Ted Hardie
CACHING editorial issue...
Jim Gettys
ISSUE: CHARSET DEFAULT
Martin J. Duerst
Re: Removing CommentURL
David W. Morris
Re: Updated proposal for CONTENT-ENCODING issue
Jeffrey Mogul
LAST CALLs, closed issues, and new HTTP/1.1 draft
Larry Masinter
Updated proposal for CONTENT-ENCODING issue
Maurizio Codogno
Re: Removing CommentURL
Maurizio Codogno
I-D ACTION:draft-ietf-http-negotiation-03.txt
Internet-Drafts@ietf.org
Streams connected to http responses?
Andreas Brusinsky
HTTP status codes (resent)
Maurizio Codogno
Sunday, 27 July
Re: Removing CommentURL
Foteos Macrides
Re: Removing CommentURL
Judson Valeski
Re: Removing CommentURL
Foteos Macrides
Re: 301/302
Roy T. Fielding
Re: Redirects
Roy T. Fielding
Re: Removing CommentURL
Jonathan Stark
Re: State Management pre-draft - combinational requirement
David W. Morris
Re: Removing CommentURL
David W. Morris
Re: OPTIONS Spec
Roy T. Fielding
Saturday, 26 July
State Management pre-draft - combinational requirement
Foteos Macrides
Re: Removing CommentURL
Judson Valeski
Re: Removing CommentURL
David W. Morris
Re: Removing CommentURL
David W. Morris
Re: Removing CommentURL
David W. Morris
Friday, 25 July
RE: 301/302
Yaron Goland
Re: Removing CommentURL
Judson Valeski
301/302
Yaron Goland
Re: Removing CommentURL
Jonathan Stark
Re: New Issue REDIRECTS
Roy T. Fielding
Re: Removing CommentURL
Judson Valeski
an (unofficial) cookie draft
Dave Kristol
RE: New Issue REDIRECTS
Jim Gettys
RE: New Issue REDIRECTS
Yaron Goland
Removing CommentURL
Larry Masinter
RE: New Issue REDIRECTS
Yaron Goland
Re: Updated proposal for CONTENT-ENCODING issue
Phillip M. Hallam-Baker
New Issue REDIRECTS
Jim Gettys
RE: can't really be LAST CALL,"HTTP State Management Mechanism (Rev1) " to Propo
Jaye, Dan
Re: Updated proposal for OPTIONS issue
Scott Lawrence
Feedback on: draft-cohen-http305306-02.txt
David W. Morris
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
David W. Morris
305/306 spec
Josh Cohen
Thursday, 24 July
Updated proposal for OPTIONS issue
Jeffrey Mogul
Updated proposal for CONTENT-ENCODING issue
Jeffrey Mogul
HTTP and friends status codes
Henning Schulzrinne
Re: CONTENT-ENCODING: FIXED revised proposed wording
Jeffrey Mogul
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Roy T. Fielding
Proposed resolution for IDEMPOTENT issue
Jeffrey Mogul
Re: HTTP status codes
Koen Holtman
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Jeffrey Mogul
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Larry Masinter
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Koen Holtman
Re: Another try at OPTIONS
Jeffrey Mogul
Re: CONTENT-ENCODING: FIXED revised proposed wording
Koen Holtman
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Koen Holtman
Re: I-D on RFC 2069 issue: digest request
John Franks
Re: Another try at OPTIONS
Scott Lawrence
Re: RETRY-AFTER HTTP working group issue...
Bob Briscoe
Additional LAST CALL issues
Larry Masinter
Wednesday, 23 July
Re: Another try at OPTIONS
Jeffrey Mogul
Re: Another try at OPTIONS
Josh Cohen
Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Joel N. Weber II
Re: Another try at OPTIONS
Scott Lawrence
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
Re: The significance of Cookies
touch@isi.edu
Re: HTTP status codes
Albert Lunde
Re: HTTP status codes
Jeffrey Mogul
Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Dave Kristol
Re: HTTP status codes
Jim Gettys
Re: The significance of Cookies
David W. Morris
Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
David W. Morris
Re: CONTENT-ENCODING: FIXED revised proposed wording
Jeffrey Mogul
The significance of Cookies
Steve Colby
Re: HTTP status codes
Joel N. Weber II
HTTP status codes
Henning Schulzrinne (BL)
can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Larry Masinter
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Dave Kristol
Re: Another try at OPTIONS
Scott Lawrence
1.1 proxies?
Scott Lawrence
Re: CONTENT-ENCODING: FIXED revised proposed wording
Martin J. Duerst
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Martin J. Duerst
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
David W. Morris
Tuesday, 22 July
CONTENT-ENCODING: FIXED revised proposed wording
Jeffrey Mogul
CONTENT-ENCODING: revised proposed wording
Jeffrey Mogul
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
Re: 305/306
Ari Luotonen
Another try at OPTIONS
Jeffrey Mogul
Re: OPTIONS Spec
Scott Lawrence
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Jeffrey Mogul
Re: Roy Fielding's comments on draft-ietf-http-hit-metering-03
Larry Masinter
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
David W. Morris
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Jonathan Stark
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Jonathan Stark
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Joel N. Weber II
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
David W. Morris
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Dave Kristol
I-D on RFC 2069 issue: digest request
Scott Lawrence
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Dave Kristol
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Larry Masinter
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Scott Lawrence
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
John Franks
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Patrick McManus
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Scott Lawrence
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Koen Holtman
SPEC 305/306
Josh Cohen
OPTIONS Spec
Josh Cohen
Monday, 21 July
Proposed solution for issue CLARIFY-NO-CACHE
Jeffrey Mogul
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Jeffrey Mogul
Re: Editorial ISSUE REMOVE_19.6
Jim Whitehead
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Joel N. Weber II
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Jeffrey Mogul
Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Phillip M. Hallam-Baker
Any objections to "Accept-encoding: gzip, *;q=0"?
Jeffrey Mogul
[Announce] PEP demo at w3c site
Eric Prud'hommeaux
Re: 305/306
Ross Patterson
RANGE-ERROR: proposed solution
Jeffrey Mogul
Re: ISSUE: LANGUAGE-TAG
Koen Holtman
Re: ISSUE CACHE-DIRECTIVE: What is the proposal?
Jeffrey Mogul
Editorial ISSUE REMOVE_19.6
Jim Gettys
Re: ISSUE: LANGUAGE-TAG
Martin J. Duerst
Q: HOWTO use different transmission schemes?
Andreas Brusinsky
Last Call: Simple Hit-Metering and Usage-Limiting for HTTP to Proposed Standard
The IESG
Saturday, 19 July
Re: STATUS100 Re: Proposed resolution
Larry Masinter
Re: draft-ietf-http-feature-reg-01.txt
Koen Holtman
ISSUE CACHE-DIRECTIVE: What is the proposal?
Koen Holtman
ISSUE QUOTED-BACK: What is the proposal?
Koen Holtman
Re: New feature tag registration drafts available
Koen Holtman
Re: draft-ietf-http-negotiation-02.txt
Koen Holtman
Re: LAST CALL on MAX-AGE issue
Roy T. Fielding
Re: ISSUE: LANGUAGE-TAG
Koen Holtman
Friday, 18 July
Re: ISSUE CONTENT-ENCODING: Proposed wording
Josh Cohen
LAST CALL on MAX-AGE issue
Jeffrey Mogul
Re: STATUS100 Re: Proposed resolution
Joel N. Weber II
Revised resolution for the STATUS100 issue
Jeffrey Mogul
Re: Proposed resolution for the STATUS100 issue
Jeffrey Mogul
Re: STATUS100 Re: Proposed resolution
Jeffrey Mogul
Re: ISSUE: LANGUAGE-TAG
Larry Masinter
Re: STATUS100 Re: Proposed resolution
David W. Morris
Re: STATUS100 Re: Proposed resolution
Koen Holtman
Re: Proposed resolution for the STATUS100 issue
Koen Holtman
RE: Proposed resolution for the STATUS100 issue
Yaron Goland
Re: ISSUE VARY: Proposed wording
Roy T. Fielding
ISSUE: LANGUAGE-TAG
Martin J. Duerst
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Roy T. Fielding
Re: STATUS100 Re: Proposed resolution
Roy T. Fielding
Re: Proposed resolution for the STATUS100 issue
Roy T. Fielding
Re: Proposed resolution for the STATUS100 issue
Pixieo2@aol.com
Re: STATUS100 Re: Proposed resolution
David W. Morris
Thursday, 17 July
Re: Proposed resolution for the STATUS100 issue
Gregory J. Woodhouse
Re: Proposed resolution for the STATUS100 issue
Jeffrey Mogul
RE: Proposed resolution for the STATUS100 issue
Yaron Goland
RE: Is 100-Continue hop-by-hop?
Yaron Goland
Re: [URN] HTTP resolution protocol
Ron Daniel, Jr.
Re: STATUS100 Re: Proposed resolution
Gregory J. Woodhouse
Re: STATUS100 Re: Proposed resolution
Jeffrey Mogul
Re: [URN] HTTP resolution protocol
John C. Mallery
Re: STATUS100 Re: Proposed resolution
rlgray@raleigh.ibm.com
Re: Proposed resolution for the STATUS100 issue
Jeffrey Mogul
Re: STATUS100 Re: Proposed resolution
Jeffrey Mogul
Re: STATUS100 Re: Proposed resolution
Jeffrey Mogul
ISSUE PROXY-AUTHORIZATION: Proposal wording
Henrik Frystyk Nielsen
Re: ISSUE VARY: Proposed wording
Henrik Frystyk Nielsen
Re: Summary of STATUS100 issue
rlgray@raleigh.ibm.com
STATUS100 Re: Proposed resolution
rlgray@raleigh.ibm.com
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Jaye, Dan
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
Re: Q: About transmission schemes ?
Ben Laurie
Q: About transmission schemes ?
Andreas Brusinsky
Re: Proposed resolution for the STATUS100 issue
Maurizio Codogno
STATUS100 Re: Proposed resolution
Scott Lawrence
exit
Dongfan Chen
305/306
Josh Cohen
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
David W. Morris
draft-ietf-http-hit-metering-03.txt
Roy T. Fielding
Wednesday, 16 July
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Dave Kristol
LAST CALL (and other status changes) on HTTP/1.1 issues
Larry Masinter
Proposed resolution for the STATUS100 issue
Jeffrey Mogul
Request IESG action for draft-ietf-http-hit-metering-03.txt
Larry Masinter
I-D ACTION:draft-ietf-http-pep-04.txt, .ps
Internet-Drafts@ietf.org
I-D ACTION:draft-ietf-http-negotiate-scenario-01.txt
Internet-Drafts@ietf.org
cache-busting doc as RFC ?
Martin Hamilton
Tuesday, 15 July
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
input on HTTP for the year 2000 working group
Neal McBurnett
New version of PEP specification available
Henrik Frystyk Nielsen
Re: draft-ietf-http-feature-reg-01.txt
Graham Klyne
Re: New feature tag registration drafts available
Graham Klyne
Re: draft-ietf-http-negotiation-02.txt
Graham Klyne
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
David W. Morris
Sunday, 13 July
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Dave Kristol
Monday, 14 July
Re: draft-ietf-http-feature-reg-01.txt
Koen Holtman
Re: New feature tag registration drafts available
Koen Holtman
Re: Content negotiation requirements
Koen Holtman
Re: draft-ietf-http-negotiation-02.txt
Koen Holtman
Sunday, 13 July
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
David W. Morris
Saturday, 12 July
Re: LAST CALL, "HTTP State Management Mechanism (Rev1)" to Propo
Foteos Macrides
Friday, 11 July
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard
Dave Kristol
Re: Is 100-Continue hop-by-hop?
Roy T. Fielding
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Yaron Goland
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Ted Hardie
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Koen Holtman
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Yaron Goland
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard
Yaron Goland
TSPECIALS: another nit
Graham Klyne
cc:Mail Link to SMTP Undeliverable Message
Ralph-W koerner
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
Matthew Rubenstein
Re: New feature tag registration drafts available
Graham Klyne
Re: Is 100-Continue hop-by-hop?
Koen Holtman
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Koen Holtman
Thursday, 10 July
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard
Yaron Goland
RE: Is 100-Continue hop-by-hop?
Yaron Goland
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Yaron Goland
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Foteos Macrides
Re: Is 100-Continue hop-by-hop?
Jeffrey Mogul
Re: New feature tag registration drafts available
Koen Holtman
Re: Is 100-Continue hop-by-hop?
Koen Holtman
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Koen Holtman
Re: Summary of STATUS100 issue
Koen Holtman
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
rlgray@raleigh.ibm.com
Re: ISSUE VARY: Proposed wording
Koen Holtman
Re: ISSUE VARY: Proposed wording
Koen Holtman
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
Larry Masinter
MUST and SHOULD, other kinds of proxies, and ISSUE PROXY-AUTHORIZATION
Larry Masinter
Re: draft-ietf-http-feature-reg-01.txt
Graham Klyne
Re: New feature tag registration drafts available
Graham Klyne
Re: Summary of STATUS100 issue
David W. Morris
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
David W. Morris
Re: ISSUE VARY: Proposed wording
David W. Morris
Re: Is 100-Continue hop-by-hop?
David W. Morris
Wednesday, 9 July
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Donald Neal
Re: ISSUE VARY: Proposed wording
Jeffrey Mogul
Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
Roy T. Fielding
Re: ISSUE VARY: Proposed wording
Jeffrey Mogul
Re: Is 100-Continue hop-by-hop?
Jeffrey Mogul
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
Matthew Rubenstein
RE: Is 100-Continue hop-by-hop?
Yaron Goland
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
Jaye, Dan
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Roy T. Fielding
RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard
Yaron Goland
Summary of STATUS100 issue
Jeffrey Mogul
Re: ISSUE CONTENT-ENCODING: Proposed wording
Koen Holtman
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Koen Holtman
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Koen Holtman
Eleventh International Unicode Conference
Misha Wolf
Tuesday, 8 July
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Phillip M. Hallam-Baker
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Henrik Frystyk Nielsen
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Dave Kristol
Re: HIT METERING to IESG on July 15
Jeffrey Mogul
Re: HIT METERING to IESG on July 15
Jeffrey Mogul
HIT METERING to IESG on July 15
Larry Masinter
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Koen Holtman
Re: ISSUE CONTENT-LOCATION: Proposed wording
Koen Holtman
Re: ISSUE VARY: Proposed wording
Henrik Frystyk Nielsen
Re: Refresh, non-standard headers, [was Re: Forcing to another page to load]
Koen Holtman
Re: Refresh, non-standard headers, [was Re: Forcing to another page to load]
David W. Morris
Re: Refresh, non-standard headers
Ross Patterson
Re: Refresh, non-standard headers, [was Re: Forcing to another page to load]
touch@isi.edu
Re-revised HTTP WG charter dates
Larry Masinter
LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
Larry Masinter
I-D ACTION:draft-ietf-http-feature-scenarios-00.txt
Internet-Drafts@ietf.org
I-D ACTION:draft-ietf-http-feature-reg-01.txt
Internet-Drafts@ietf.org
I-D ACTION:draft-ietf-http-hit-metering-03.txt
Internet-Drafts@ietf.org
Monday, 7 July
Refresh, non-standard headers, [was Re: Forcing to another page to load]
Larry Masinter
Is 100-Continue hop-by-hop?
Jeffrey Mogul
New feature tag registration drafts available
Koen Holtman
Re: ISSUE VARY: Proposed wording
Koen Holtman
Re: SAFE, UAHINT and other things not part of HTTP/1.1 now
Foteos Macrides
Re: SAFE, UAHINT and other things not part of HTTP/1.1 now
Koen Holtman
Re: ISSUE VARY: Proposed wording
Maurizio Codogno
Re: Content negotiation requirements
Graham Klyne
Sunday, 6 July
SAFE, UAHINT and other things not part of HTTP/1.1 now
Larry Masinter
Re: ISSUE CONTENT-ENCODING: Proposed wording
Henrik Frystyk Nielsen
Re: Forcing to another page to load
Rob
Re: Forcing to another page to load
Warren P. Chi
Re: Forcing to another page to load
debbie eidelman
Re: Forcing to another page to load
Andrew Daviel
Wednesday, 2 July
Re: HTTP/1.1 & Proxies
Graham Klyne
Friday, 4 July
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
David W. Morris
Re: Proposal: 100-Continue optional under Client control
Joel N. Weber II
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Koen Holtman
Re: Proposal: 100-Continue optional under Client control
David W. Morris
Re: Proposal: 100-Continue optional under Client control
Koen Holtman
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
David W. Morris
Re: GET and referer security considerations
Koen Holtman
Re: Proposal: 100-Continue optional under Client control
David W. Morris
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Koen Holtman
Re: ISSUE CONTENT-ENCODING: Proposed wording
Koen Holtman
Re: Revised HTTP WG charter dates
Koen Holtman
Re: Content negotiation requirements
Koen Holtman
Re: Interesting stats on the prevalence of bogus Last-Modified times
Andrew Daviel
Content negotiation requirements
Graham Klyne
Re: feature registration expired
Koen Holtman
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
David W. Morris
Re: GET and referer security considerations
David W. Morris
Thursday, 3 July
Interesting stats on the prevalence of bogus Last-Modified times
Jeffrey Mogul
feature registration expired
Larry Masinter
LAST CALL on four issues from http://www.w3.org/pub/WWW/Protocols/HTTP/Issues/
Larry Masinter
Re: ISSUE CONTENT-ENCODING: Proposed wording
Graham Klyne
Revised HTTP WG charter dates
Larry Masinter
Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
Dave Kristol
ISSUE VARY: Proposed wording
Henrik Frystyk Nielsen
ISSUE PROXY-AUTHORIZATION: Proposal wording
Henrik Frystyk Nielsen
ISSUE CONTENT-LOCATION: Proposed wording
Henrik Frystyk Nielsen
ISSUE CONTENT-ENCODING: Proposed wording
Henrik Frystyk Nielsen
Re: draft-ietf-http-negotiation-02.txt
Graham Klyne
Re: GET and referer security considerations
Patrick McManus
Re: HTTP/1.1 & Proxies
Graham Klyne
Re: GET and referer security considerations
David W. Morris
Wednesday, 2 July
Re: GET and referer security considerations
Andrew Daviel
Re: Proposal: 100-Continue optional under Client control
Scott Lawrence
Re: Proposal: 100-Continue optional under Client control
Jeffrey Mogul
Re: HTTP/1.1 & Proxies
Roy T. Fielding
Re: HTTP/1.1 & Proxies
Roy T. Fielding
Re: HTTP/1.1 & Proxies
Roy T. Fielding
Re: Proposal: 100-Continue optional under Client control
Jeffrey Mogul
Re: GET and referer security considerations
Scott Lawrence
Re: GET and referer security considerations
Matthew Rubenstein
Re: GET and referer security considerations
Siew Sim
Re: GET and referer security considerations
Foteos Macrides
Re: GET and referer security considerations
Koen Holtman
Re: HTTP/1.1 & Proxies
Henrik Frystyk Nielsen
Re: HTTP/1.1 & Proxies
Josh
Re: GET and referer security considerations
Ross Patterson
Re: HTTP/1.1 & Proxies
Graham Klyne
Re: HTTP/1.1 & Proxies
Graham Klyne
Re: HTTP/1.1 & Proxies
Josh Cohen
Re: HTTP/1.1 & Proxies
Graham Klyne
Re: HTTP/1.1 & Proxies
Josh Cohen
Re: HTTP/1.1 & Proxies
Larry Masinter
Re: HTTP/1.1 & Proxies
Josh Cohen
Re: HTTP/1.1 & Proxies
Larry Masinter
Tuesday, 1 July
Re: GET and referer security considerations
Larry Masinter
Re: HTTP/1.1 & Proxies
Roy T. Fielding
Re: GET and referer security considerations
David W. Morris
RE: HTTP/1.1 & Proxies
Yaron Goland
Re: GET and referer security considerations
Scott Lawrence
Re: HTTP/1.1 & Proxies
Henrik Frystyk Nielsen
GET and referer security considerations
Koen Holtman
Re: Assigned paths
Graham Klyne
Re: Digest Authentication bleat
Phillip M. Hallam-Baker
Re: HTTP/1.1 & Proxies
Josh
HTTP/1.1 & Proxies
Yaron Goland
Monday, 30 June
Re: 305/306 response codes
Koen Holtman
RE: Digest Authentication bleat
Fisher Mark
Re: Proposal: 100-Continue optional under Client control
Koen Holtman
Re: Assigned paths
Hallam-Baker
Re: Assigned paths
Jeff de la Beaujardiere
Proposal: 100-Continue optional under Client control
David W. Morris
Friday, 27 June
Re: Assigned paths
Graham Klyne
Updated test implementation for TCN available
Koen Holtman
Re: Assigned paths
Larry Masinter
Re: Status 100
David W. Morris
Thursday, 26 June
RE: confidentiality and the referer field
Michael Giroux
Re: confidentiality and the referer field
Hallam-Baker
RE: confidentiality and the referer field
Michael Giroux
Re: confidentiality and the referer field
Ross Patterson
Re: confidentiality and the referer field
Matthew Rubenstein
Re: confidentiality and the referer field
Ross Patterson
Digest Authentication bleat
Dave Kristol
Re: confidentiality and the referer field
Ross Patterson
Re: Status 100
John Franks
Re: confidentiality and the referer field
Hallam-Baker
Status 100
rlgray@raleigh.ibm.com
Re: confidentiality and the referer field
Matthew Rubenstein
Re: confidentiality and the referer field
Hallam-Baker
Re: confidentiality and the referer field
Ross Patterson
Re: Assigned paths
Ross Patterson
Re: confidentiality and the referer field
David W. Morris
Re: Assigned paths
David W. Morris
confidentiality and the referer field
Hallam-Baker
Re: Assigned paths
Roy T. Fielding
Assigned paths
Ross Patterson
Tuesday, 24 June
Re: Transient content negotiation
Koen Holtman
I-D ACTION:draft-ietf-http-state-man-mec-02.txt, .ps
Internet-Drafts@ietf.org
I-D ACTION:draft-ietf-http-state-man-mec-02.txt, .ps
Internet-Drafts@ietf.org
Monday, 23 June
I-D ACTION:draft-cohen-http-305-306-responses-00.txt
Internet-Drafts@ietf.org
I-D ACTION:draft-ietf-http-negotiate-scenario-00.txt
Internet-Drafts@ietf.org
draft-ietf-http-negotiate-scenario.00.txt
Graham Klyne
Sunday, 22 June
Re: Transient content negotiation
Graham Klyne
Re: Transient content negotiation
Graham Klyne
Saturday, 21 June
Re: More thoughts on content negotiation
Koen Holtman
HTTP Download
Malcolm Messiter
Friday, 20 June
Re: Transient content negotiation
Larry Masinter
Re: Transient content negotiation
Koen Holtman
Thursday, 19 June
new cookie I-D submitted
Dave Kristol
Re: COMMENT: LAST CALL comment
Koen Holtman
Re: First draft of negotiation requirements document
Ted Hardie
Web Security
Alessandro Monteiro Lima
Wednesday, 18 June
Re: First draft of negotiation requirements document
Larry Masinter
More thoughts on content negotiation
Graham Klyne
Transient content negotiation
Graham Klyne
Re: First draft of negotiation requirements document
Koen Holtman
Tuesday, 17 June
Re: 305/306 response codes
Larry Masinter
Re: First draft of negotiation requirements document
Ted Hardie
Re: First draft of negotiation requirements document
Ted Hardie
Re: First draft of negotiation requirements document
Koen Holtman
Re: 305/306 response codes
Koen Holtman
Re: First draft of negotiation requirements document
Scott Lawrence
Re: 305/306 response codes
Koen Holtman
I-D ACTION:draft-ietf-http-negotiate-scenario-00.txt
Internet-Drafts@ietf.org
Sunday, 15 June
Re: 305/306 response codes
Roy T. Fielding
Re: COMMENT: LAST CALL comment
Roy T. Fielding
Re: OPTIONS method
Roy T. Fielding
Re: OPTIONS method
David W. Morris
Re: COMMENT: LAST CALL comment
Koen Holtman
Re: Proposal: Vary on Cookies
Koen Holtman
Re: OPTIONS method
Josh
Saturday, 14 June
Re: Proposal: Vary on Cookies
Josh
Friday, 13 June
First draft of negotiation requirements document
Ted Hardie
Re: Proposal: Vary on Cookies
Koen Holtman
Re: Proposal: Vary on Cookies
Larry Masinter
Re: Proposal: Vary on Cookies
David W. Morris
Thursday, 12 June
Re: Proposal: Vary on Cookies
Richard Vermillion
Re: Proposal: Vary on Cookies
David W. Morris
Proposal: Vary on Cookies
Richard Vermillion
Is Your Web Site A Secret?
owl@owlsnest.com
Re: 305/306 response codes
Ross Patterson
Re: MUST a client wait for 100 when doing PUT or POST?
Pixieo2@aol.com
Wednesday, 11 June
Re: 305/306 response codes
Josh Cohen
Re: 305/306 response codes
Jeffrey Mogul
Re: COMMENT: LAST CALL comment
Roy T. Fielding
Re: A new suggestion on 100 CONTINUE
Roy T. Fielding
Re: cache-busting and charsets again
Roy T. Fielding
Re: cache-busting and charsets again
Koen Holtman
Re: A new suggestion on 100 CONTINUE
John Franks
Re: A new suggestion on 100 CONTINUE
Roy T. Fielding
Re: cache-busting document
Koen Holtman
Re: A new suggestion on 100 CONTINUE
John Franks
Re: Question
Ben Laurie
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST
Koen Holtman
Buggy TCP implementations. Was: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Jim Gettys
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Roy T. Fielding
Re: MUST a client wait for 100 when doing PUT or POST?
Roy T. Fielding
Re: Question
Luigi Rizzo
Re: Question
Jeffrey Mogul
Re: Proxy Keep-Alive
Anawat Chankhunthod
Tuesday, 10 June
Proxy Keep-Alive
Andrew Goodman
Wednesday, 11 June
Re: A new suggestion on 100 CONTINUE
David W. Morris
Re: A new suggestion on 100 CONTINUE
David W. Morris
Re: charsets again
Martin J. Duerst
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
David W. Morris
Re: OPTIONS method
Roy T. Fielding
Re: MUST a client wait for 100 when doing PUT or POST?
Scott Lawrence
Re: cache-busting and charsets again
Roy T. Fielding
Re: A new suggestion on 100 CONTINUE
Scott Lawrence
Re: MUST a client wait for 100 when doing PUT or POST?
David W. Morris
Re: A new suggestion on 100 CONTINUE
John Franks
charsets again
Wojtek Sylwestrzak
Re: A new suggestion on 100 CONTINUE
George Carrette
A new suggestion on 100 CONTINUE
John Franks
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Henrik Frystyk Nielsen
Re: MUST a client wait for 100 when doing PUT or POST?
Scott Lawrence
RE: MUST a client wait for 100 when doing PUT or POST?
John Franks
Re: cache-busting and charsets again
Martin J. Duerst
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
Anselm Baird_Smith
Tuesday, 10 June
Re: cache-busting document
Drazen Kacar
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
David W. Morris
cache-busting and charsets again
W.Sylwestrzak@icm.edu.pl
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
Randy Turner
cache-busting and charsets again
W.Sylwestrzak@icm.edu.pl
Re: cache-busting document
W.Sylwestrzak@icm.edu.pl
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
Paul Leach
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
David W. Morris
Re: cache-busting document
Andrew Daviel
RE: 305/306 response codes
Yaron Goland
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
David W. Morris
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
Paul Leach
RE: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Wingard, Steve
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Roy T. Fielding
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
John Franks
Re: New feature negotiation syntax
Koen Holtman
Re: New feature negotiation syntax
Koen Holtman
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Scott Lawrence
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Josh Cohen
Unidentified subject!
P.Lister@cranfield.ac.uk
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
John Franks
Re: New feature negotiation syntax
David W. Morris
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Henrik Frystyk Nielsen
Feature negotiation requirements
Daniel LaLiberte
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
John Franks
Re: New feature negotiation syntax
Jim Gettys
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
David W. Morris
Re: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Henrik Frystyk Nielsen
Re: cache-busting document
David W. Morris
Re: 305/306 response codes
Scott Lawrence
ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
Henrik Frystyk Nielsen
Re: cache-busting document
P.Lister@cranfield.ac.uk
Re: cache-busting document
Jon Knight
Re: cache-busting document
P.Lister@cranfield.ac.uk
Re: cache-busting document
Andrew Daviel
Monday, 9 June
Web Site Visibility
message@marketcom2.com
cache-busting document
Shel Kaphan
Question
Sami Iren
Sunday, 8 June
Re: cache-busting document
Drazen Kacar
Re: cache-busting document
Drazen Kacar
Saturday, 7 June
Re: 305/306 response codes
Josh Cohen
Re: cache-busting document
W.Sylwestrzak@icm.edu.pl
Re: cache-busting document
David W. Morris
Re: cache-busting document
David W. Morris
Sunday, 8 June
Re: cache-busting document
Wojtek Sylwestrzak
Saturday, 7 June
Re: draft-ietf-http-negotiation-02.txt
Koen Holtman
Re: cache-busting document
Drazen Kacar
Re: cache-busting document
Ben Laurie
Re: cache-busting document
Larry Masinter
cache-busting document
Martin Hamilton
Re: New feature negotiation syntax
Koen Holtman
Re: 305/306 response codes
Drazen Kacar
Friday, 6 June
OPTIONS method
Josh Cohen
RE: 305/306 response codes
Josh Cohen
RE: New feature negotiation syntax
Yaron Goland
Re: New feature negotiation syntax
Ted Hardie
Re: New feature negotiation syntax
Ted Hardie
305/306 response codes
Josh Cohen
RE: New feature negotiation syntax
Yaron Goland
RE: New feature negotiation syntax
Yaron Goland
RE: New feature negotiation syntax
Yaron Goland
Graham Klyne on content negotiation
Larry Masinter
draft-mutz-http-attributes-02.txt
Graham Klyne
draft-ietf-http-negotiation-02.txt
Graham Klyne
Re: New feature negotiation syntax
Koen Holtman
Re: New feature negotiation syntax
Larry Masinter
Re: New feature negotiation syntax
Koen Holtman
Re: HTTP/1.1 -- who disconnects the session?
David W. Morris
Thursday, 5 June
Persistent connections, and 1.0 browsers
Michael Giroux
Re: HTTP/1.1 -- who disconnects the session?
Josh Cohen
HTTP/1.1 -- who disconnects the session?
Michael Giroux
Re: COMMENT: LAST CALL comment
Larry Masinter
RANGE-ERROR issue: proposed resolution
Jeffrey Mogul
Re: COMMENT: resolution
Koen Holtman
Re: New feature negotiation syntax
Dave Kristol
Re: New feature negotiation syntax
Koen Holtman
Re: New feature negotiation syntax
Koen Holtman
Wednesday, 4 June
Re: New feature negotiation syntax
Joel N. Weber II
Re: New feature negotiation syntax
Ted Hardie
Re: New feature negotiation syntax
Larry Masinter
Re: COMMENT: LAST CALL comment
David W. Morris
Re: New feature negotiation syntax
Koen Holtman
Re: New feature negotiation syntax
Koen Holtman
Re: COMMENT: LAST CALL comment
Ross Patterson
Re: New feature negotiation syntax
Larry Masinter
Re: COMMENT: LAST CALL comment
David W. Morris
Re: New feature negotiation syntax
David W. Morris
Re: COMMENT: LAST CALL comment
Ross Patterson
Re: New feature negotiation syntax
Larry Masinter
Tuesday, 3 June
Re: New feature negotiation syntax
Scott Lawrence
Re: New feature negotiation syntax
Larry Masinter
Monday, 2 June
Re: An experiment in producing RFC1122-style requirements checklist
David W. Morris
Re: An experiment in producing RFC1122-style requirements checklist
Josh Cohen
Re: An experiment in producing RFC1122-style requirements checklist
Albert Lunde
Re: An experiment in producing RFC1122-style requirements checklist
rlgray@raleigh.ibm.com
Sunday, 1 June
Re: New feature negotiation syntax
Scott Lawrence
Re: New feature negotiation syntax
Koen Holtman
Re: New feature negotiation syntax
Larry Masinter
Saturday, 31 May
Re: New feature negotiation syntax
Koen Holtman
Date/time on the Internet
Misha Wolf
Re: New feature negotiation syntax
Larry Masinter
Friday, 30 May
Re: NS, Verisign, Firefly proposal [was Re: Revised charter ,milestones
Hallam-Baker
RE: NS, Verisign, Firefly proposal [was Re: Revised charter ,milestones
Jaye, Dan
Re: Common Gateway Interface
David W. Morris
Re: Common Gateway Interface
Hallam-Baker
Re: Q: protocolls and fault tolerance
touch@isi.edu
Re: New feature negotiation syntax
Larry Masinter
Re: Common Gateway Interface
Dylan Barrell
Re: An experiment in producing RFC1122-style requirements checklist
Scott Lawrence
Re: An experiment in producing RFC1122-style requirements checklist
Ross Patterson
Re: Q: protocolls and fault tolerance
Andreas Brusinsky
Re: Common Gateway Interface
Scott Lawrence
Re: New feature negotiation syntax
Koen Holtman
Re: NS, Verisign, Firefly proposal [was Re: Revised charter ,
Koen Holtman
Re: Common Gateway Interface
Dylan Barrell
Thursday, 29 May
Re: Q: protocolls and fault tolerance
touch@isi.edu
Q: protocolls and fault tolerance
Andreas Brusinsky
Re: Common Gateway Interface
Carlos A. Varela
Re: Common Gateway Interface
John C. Mallery
RE: An experiment in producing RFC1122-style requirements checkli st
Yaron Goland
Re: Common Gateway Interface
Hallam-Baker
Common Gateway Interface
Dylan Barrell
Re: An experiment in producing RFC1122-style requirements checklist
Ben Laurie
An experiment in producing RFC1122-style requirements checklist
Jeffrey Mogul
Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
Larry Masinter
Re: New feature negotiation syntax
Larry Masinter
Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
guthery@austin.sar.slb.com
Wednesday, 28 May
Re: NS, Verisign, Firefly proposal [was Re: Revised charter ,
Hallam-Baker
Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
Paul Hoffman
Re: NS, Verisign, Firefly proposal [was Re: Revised charter , milestones
David W. Morris
Re: Revised charter milestones
Benjamin Franz
Re: Revised charter milestones
Larry Masinter
OPS specification
Ted Hardie
Re: Revised charter milestones
Koen Holtman
Re: Comment on PEP draft
carl f GRIFFITH
Cookie domain
carl f GRIFFITH
Re: Comment on PEP draft
Koen Holtman
Cookie domain
carl f GRIFFITH
Cookie domain
Iole Pansino
HTTP 1.1 Issue: 403VS404
Ross Patterson
I-D ACTION:draft-ietf-http-negotiation-02.txt
Internet-Drafts@ietf.org
Re: New feature negotiation syntax
Koen Holtman
Re: URI -> URL when talking about 'moved ...'
Mike_Spreitzer.PARC@xerox.com
Re: URI -> URL when talking about 'moved ...'
Larry Masinter
URI -> URL when talking about 'moved ...'
Larry Masinter
Re: New feature negotiation syntax
Larry Masinter
Monday, 26 May
Re: Rewrite of feature tag syntax rules
Koen Holtman
New content negotiation draft: draft-ietf-http-negotiation-02.txt
Koen Holtman
Revised charter milestones
Larry Masinter
Sunday, 25 May
COMMENT: resolution
Larry Masinter
Re: New feature negotiation syntax
Scott Lawrence
Re: notes from previous Editing Group meeting: goals, docking
Koen Holtman
COMMENT: LAST CALL comment
Koen Holtman
Saturday, 24 May
Re: HTTP 1.1 Issue: When To Close Connections
Larry Masinter
Friday, 23 May
RE: PEP Integration in RTSP
Yaron Goland
notes from previous Editing Group meeting: goals, docking
Larry Masinter
RE: PEP Integration in RTSP
Yaron Goland
HTTP Issues LAST CALL; HTTP editing group
Larry Masinter
RE: PEP Integration in RTSP
Yaron Goland
RE: PEP Integration in RTSP
Yaron Goland
Re: HTTP 1.1 Issue: When To Close Connections
Dave Kristol
RE: PEP Integration in RTSP
Yaron Goland
HTTP 1.1 Issue: When To Close Connections
John C. Mallery
RE: PEP Integration in RTSP
Yaron Goland
RE: New feature negotiation syntax
Yaron Goland
Re: Rewrite of feature tag syntax rules
Martin J. Duerst
Thursday, 22 May
Re: Rewrite of feature tag syntax rules
Larry Masinter
Re: DES attack, help crack bad encryption!
carl f GRIFFITH
Re: DES attack, help crack bad encryption!
Harald.T.Alvestrand@uninett.no
Re: Rewrite of feature tag syntax rules
Martin J. Duerst
Re: Rewrite of feature tag syntax rules
Martin J. Duerst
Tuesday, 20 May
DES attack, help crack bad encryption!
Anonymous
Monday, 19 May
Call for comments on feature tag syntax
Koen Holtman
Re: Rewrite of feature tag syntax rules
Henrik Frystyk Nielsen
Re: Comment on PEP draft
Henrik Frystyk Nielsen
Re: Rewrite of feature tag syntax rules
Koen Holtman
Re: Rewrite of feature tag syntax rules
Koen Holtman
Re: Rewrite of feature tag syntax rules
Henrik Frystyk Nielsen
Re: Rewrite of feature tag syntax rules
Koen Holtman
Re: PEP Integration in RTSP
Henrik Frystyk Nielsen
Re: Rewrite of feature tag syntax rules
Jeffrey Mogul
Re: Rewrite of feature tag syntax rules
Larry Masinter
Re: PEP Integration in RTSP
Koen Holtman
Re: RANGES (Might be nice to allow 206 response to range request
Koen Holtman
Re: Comment on PEP draft
Koen Holtman
Re: Issue: BYTE-RANGE (Is the right meta-data returned on range
Koen Holtman
Re: Rewrite of feature tag syntax rules
Koen Holtman
Re: Rewrite of feature tag syntax rules
Koen Holtman
Saturday, 17 May
Re: PEP Integration in RTSP
Ross Patterson
Re: PEP Integration in RTSP
Henning Schulzrinne
Friday, 16 May
Re: Rewrite of feature tag syntax rules
Larry Masinter
Re: PEP Integration in RTSP
Ross Patterson
Re: Rewrite of feature tag syntax rules
Roy T. Fielding
PEP Integration in RTSP
Rob Lanphier
Re: Rewrite of feature tag syntax rules
Martin J. Duerst
Re: WEB->FAX
Luis Alberto Caceres
Re: Rewrite of feature tag syntax rules
Albert Lunde
Re: Rewrite of feature tag syntax rules
Koen Holtman
Re: Rewrite of feature tag syntax rules
Koen Holtman
Thursday, 15 May
Re: WEB->FAX
Eric Harley
Re: WEB->FAX
Eric Harley
FREE LISTING in Worldwide Directory
Act Now For Your
Re: Rewrite of feature tag syntax rules
Roy T. Fielding
WEB->FAX
Luis Alberto Caceres
Re: Rewrite of feature tag syntax rules
Larry Masinter
Re: Rewrite of feature tag syntax rules
Koen Holtman
Re: Rewrite of feature tag syntax rules
Martin J. Duerst
Announcement: A new Wiley book on World Wide Web Security
Avi Rubin
Re: Rewrite of feature tag syntax rules
David W. Morris
Re: Rewrite of feature tag syntax rules
David W. Morris
I-D ACTION:draft-ietf-http-jaye-trust-state-00.txt
Internet-Drafts@ietf.org
Re: Rewrite of feature tag syntax rules
Koen Holtman
Re: Rewrite of feature tag syntax rules
Koen Holtman
Re: Rewrite of feature tag syntax rules
Larry Masinter
Re: Rewrite of feature tag syntax rules
David W. Morris
Wednesday, 14 May
Re: draft-daviel-metadata-link-00.txt
Jim Whitehead
draft-daviel-metadata-link-00.txt
Andrew Daviel
Re: feature negotiation syntax
Koen Holtman
Rewrite of feature tag syntax rules
Koen Holtman
Re: feature negotiation syntax
Martin J. Duerst
Re: feature negotiation syntax
Larry Masinter
Re: feature negotiation syntax
Martin J. Duerst
references to obsolete RFC1522
Jeff de la Beaujardiere
Document Action: Use and interpretation of HTTP version numbers to Informational
The IESG
Tuesday, 13 May
Re: feature negotiation syntax
Henrik Frystyk Nielsen
Re: feature negotiation syntax
Larry Masinter
Re: feature negotiation syntax
David W. Morris
Re: feature negotiation syntax
Larry Masinter
Monday, 12 May
Re: New feature negotiation syntax
Scott Lawrence
Re: New feature negotiation syntax
Koen Holtman
Re: feature negotiation syntax
Koen Holtman
RANGES (Might be nice to allow 206 response to range request without knowing total content length)
Henrik Frystyk Nielsen
Issue: 304-LAST-MODIFIED (Should 304 include Last Modified?)
Henrik Frystyk Nielsen
Issue: BYTE-RANGE (Is the right meta-data returned on range requests?)
Henrik Frystyk Nielsen
Re: Issue: BYTE-RANGE -- resolved?
Henrik Frystyk Nielsen
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Henrik Frystyk Nielsen
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Benjamin Franz
request for input of managing WWW-servers.
Harrie Hazewinkel
Sunday, 11 May
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Roy T. Fielding
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Josh Cohen
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Roy T. Fielding
Saturday, 10 May
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Dave Kristol
Re: NUDGE: Our piece on Host: and URLs (Fwd)
David W. Morris
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Benjamin Franz
Re: NUDGE: Our piece on Host: and URLs (Fwd)
David W. Morris
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Roy T. Fielding
Re: NUDGE: Our piece on Host: and URLs (Fwd)
Josh Cohen
Friday, 9 May
Issue: BYTE-RANGE -- resolved?
Dave Kristol
"versions" -> Informational RFC
Larry Masinter
Thursday, 8 May
Re: New feature negotiation syntax
Larry Masinter
RE: New feature negotiation syntax
Yaron Goland
Re: Comment on PEP draft
Henrik Frystyk Nielsen
Re: New feature negotiation syntax
Larry Masinter
feature negotiation syntax
Larry Masinter
Wednesday, 7 May
Re: Indexing non-HTML objects