Saturday, 27 September 1997
Friday, 26 September 1997
- HTTP-WG recommends "SAFE" and "UAHINT" for "Experimental"
- Re: Age calculation in HTTP: two Internet Drafts
Wednesday, 24 September 1997
- Re: Weekly Internet HTTP/1.1 Tests
- Weekly Internet HTTP/1.1 Tests
- Re: some thoughts on extensions on REQUEST line.
- Re: some thoughts on extensions on REQUEST line.
- Re: some thoughts on extensions on REQUEST line.
- Re: some thoughts on extensions on REQUEST line.
- some thoughts on extensions on REQUEST line.
Tuesday, 23 September 1997
Saturday, 24 August 1996
Tuesday, 23 September 1997
- Re: Age calculation in HTTP: two Internet Drafts
- Re: draft-ietf-http-state-man-mec-03: $Version and path
- Re: draft-ietf-http-state-man-mec-03: $Version and path
- Re: draft-ietf-http-state-man-mec-03: $Version and path
Monday, 22 September 1997
- Re: draft-ietf-http-state-man-mec-03: $Version and path
- Proposal for Weekly Internet HTTP/1.1 Tests
- req-sum-00
- Interoperability Test Survey (updated)
Saturday, 20 September 1997
- Re: SSL Tunneling; Informational RFC; Last call?
- Re: SSL Tunneling; Informational RFC; Last call?
- Re: Interest in standard HTTP headers for specifying client
Friday, 19 September 1997
- Re: Interest in standard HTTP headers for specifying client
- Re: SSL Tunneling; Informational RFC; Last call?
- Re: I-D ACTION:draft-ietf-http-req-sum-00.txt
- Re: I-D ACTION:draft-ietf-http-req-sum-00.txt
- Re: draft-ietf-http-state-man-mec-03: $Version and path
- Re: Interest in standard HTTP headers for specifying client
Thursday, 18 September 1997
- RE: draft-ietf-http-req-sum-00.txt
- Re: draft-ietf-http-req-sum-00.txt
- Re: Interest in standard HTTP headers for specifying client display attributes?
- RE: Globally unique e-tags, if-match on content-ID, etc.
- Re: draft-ietf-http-state-man-mec-03: $Version and path
- RE: Head response Transfer-Encoding: chunked?
- Re: Head response Transfer-Encoding: chunked?
- Re: Interest in standard HTTP headers for specifying client display attributes?
- Re: Age calculation in HTTP: two Internet Drafts
- RE: comments on jaye-trust-state-01
- Re: Interest in standard HTTP headers for specifying client display attributes?
- Re: Head response Transfer-Encoding: chunked?
Wednesday, 17 September 1997
- RE: SSL Tunneling; Informational RFC; Last call?
- Interoperability Test Survey
- Interest in standard HTTP headers for specifying client display attributes?
- Re: Head response Transfer-Encoding: chunked?
- I-D ACTION:draft-ietf-http-uahint-01.txt
- Re: SSL Tunneling; Informational RFC; Last call?
- [Fwd: I-D ACTION:draft-lyon-itp-nodes-02.txt]
- RE: Last-Modified in chunked footer
- Re: SSL Tunneling; Informational RFC; Last call?
Tuesday, 16 September 1997
- Re: SSL Tunneling; Informational RFC; Last call?
- RE: Last-Modified in chunked footer
- RE: Last-Modified in chunked footer
Monday, 15 September 1997
Tuesday, 16 September 1997
- Re: SSL Tunneling; Informational RFC; Last call?
- Age calculation in HTTP: two Internet Drafts
- I-D ACTION:draft-ietf-http-negotiation-04.txt
- Re: Last-Modified in chunked footer
- RE: Last-Modified in chunked footer
- Re: SSL Tunneling; Informational RFC; Last call?
- I-D ACTION:draft-ietf-http-alternates-00.txt
- I-D ACTION:draft-ietf-http-req-sum-00.txt
- Revised UA HINT Draft Submitted
Monday, 15 September 1997
- Re: Last-Modified in chunked footer
- Re: indefinite server-push (was 'Last-Modified in chunked footer')
- draft-ietf-http-state-man-mec-03: $Version and path
- Re: SSL Tunneling; Informational RFC; Last call?
- Re: Proxy
- RE: indefinite server-push (was 'Last-Modified in chunked footer')
- RE: Last-Modified in chunked footer
- Re: Globally unique e-tags, if-match on content-ID, etc.
- RE: indefinite server-push (was 'Last-Modified in chunked footer' )
- Re: indefinite server-push (was 'Last-Modified in chunked footer')
- Re: Clock skew and the importance of clock synchronization in HTTP servers.
- Re: indefinite server-push (was 'Last-Modified in chunked footer')
- New content negotiation drafts available
- Re: indefinite server-push (was 'Last-Modified in chunked footer')
- RE: indefinite server-push (was 'Last-Modified in chunked footer')
- Re: Last-Modified in chunked footer
- Re: indefinite server-push (was 'Last-Modified in chunked footer')
- RE: indefinite server-push (was 'Last-Modified in chunked footer')
- indefinite server-push (was 'Last-Modified in chunked footer')
- Proxy
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- RE: Last-Modified in chunked footer
- RE: Globally unique e-tags, if-match on content-ID, etc.
- RE: Globally unique e-tags, if-match on content-ID, etc.
Saturday, 13 September 1997
Friday, 12 September 1997
- SSL Tunneling; Informational RFC; Last call?
- Re: Clock skew and the importance of clock synchronization in HTTP servers.
- I-D ACTION:draft-holtman-http-safe-03.txt (fwd)
- Re: Clock skew and the importance of clock synchronization in HTTP servers.
- Clock skew and the importance of clock synchronization in HTTP servers.
- RE: comments on jaye-trust-state-01
Thursday, 11 September 1997
- Revised http://www.w3.org/Protocols/HTTP/Issues/
- Re: Content-Coding on POST
- Re: Content-Coding on POST
- Content-Coding on POST
- Re: Compressing HTML
Wednesday, 10 September 1997
Tuesday, 9 September 1997
- Re: Comments on I-D ACTION:draft-ietf-http-options-02.txt
- Re: DATE-IF-MODIFIED
- Re: Last-Modified in chunked footer
- Re: Basic Authentication behavior
- Comments on I-D ACTION:draft-ietf-http-options-02.txt
Monday, 8 September 1997
- Re: 301/302
- Re: Basic Authentication behavior
- Re: Last-Modified in chunked footer
- Re: Basic Authentication behavior
- Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: Last-Modified in chunked footer
- Re: Basic Authentication behavior
- RE: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: Basic Authentication behavior
- Re: 301/302
- Re: 301/302
- Re: Basic Authentication behavior
- Re: Basic Authentication behavior
- Re: Basic Authentication behavior
- Re: FW: revised trusted cookie spec
- Safe header -> experimental RFC
- Re: DATE-IF-MODIFIED
- Re: DATE-IF-MODIFIED
Saturday, 6 September 1997
Monday, 8 September 1997
Sunday, 7 September 1997
- Re: Basic Authentication behavior
- RE: Last-Modified in chunked footer
- RE: Last-Modified in chunked footer
- Re: Basic Authentication behavior
Friday, 5 September 1997
- Re: Last-Modified in chunked footer
- Re: 301/302
- Re: 301/302
- extensibility of status codes (was: 301/302)
- Re: 301/302
- Re: Last-Modified in chunked footer
- Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: DATE-IF-MODIFIED
- Re: 301/302
- Re: 301/302
- DATE-IF-MODIFIED
- Re: 301/302
- Re: 301/302
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- tcpdump
- TCP spoofing
- Re: Basic Authentication behavior
Thursday, 4 September 1997
- Alternates?
- Re: Last-Modified in chunked footer
- (revised) Minutes, HTTP Working Group, Munich IETF Aug 11-12
- Re: 301/302
- Re: RE-VERSION
- Re: Last-Modified in chunked footer
- Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: RE-VERSION
- Re: 301/302
- Re: Last-Modified in chunked footer
- Re: RE-VERSION
- Re: 301/302
- RE: 301/302
- (tangent) Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: 301/302
- RE-VERSION
- Re: 301/302
- Re: 301/302
- Re: 301/302
Wednesday, 3 September 1997
- web login session transfer?
- Re: 301/302
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- RE: 301/302
- Re: 301/302
- Re: Last-Modified in chunked footer
- Re: 301/302
- Re: Last-Modified in chunked footer
- Re: 301/302
- RE: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: 301/302
- Re: 301/302
- Re: Spelling of "cachable"
- Re: 301/302
- Re: Last-Modified in chunked footer
- Re: Last-Modified in chunked footer
- Re: FW: revised trusted cookie spec
- Re: Last-Modified in chunked footer
- I-D ACTION:draft-ietf-http-options-02.txt
- Re: Spelling of "cachable"
- Re: Last-Modified in chunked footer
- Last-Modified in chunked footer
- Re: 301/302
- Re: Spelling of "cachable"
- RE: 301/302
- RE: 301/302
- RE: 301/302
- RE: 301/302
- Re: Spelling of "cachable"
- [Fwd: RFC 2183 on Content-Disposition]
Tuesday, 2 September 1997
- Re: Spelling of "cachable"
- Re: Basic Authentication behavior
- Re: Basic Authentication behavior
- Re: FW: revised trusted cookie spec
- Re: Basic Authentication behavior
- Re: Basic Authentication behavior
- Re: Spelling of "cachable"
- Basic Authentication behavior
- Proposed Standard for Alternates header
- HTTP POST and Cookies
- Spelling of "cachable"
- Re: Issue SAFE
- Re: Interoperability Event
Monday, 1 September 1997
Sunday, 31 August 1997
Saturday, 30 August 1997
Friday, 29 August 1997
- Re: 301/302
- Re: 301/302
- Re: Interoperability Event
- Re: 301/302
- Re: Interoperability Event
- Re: 301/302
- Re: Interoperability Event
- Re: Interoperability Event
- Re: Interoperability Event
- Re: 301/302
- Re: 301/302
- Interoperability Event
- Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: 301/302
Thursday, 28 August 1997
Wednesday, 27 August 1997
Friday, 22 August 1997
Thursday, 21 August 1997
Tuesday, 19 August 1997
- comments on jaye-trust-state-01
- Re: FW: revised trusted cookie spec
- Re: FW: revised trusted cookie spec
- Re: FW: revised trusted cookie spec
- RE: FW: revised trusted cookie spec
- Re: FW: revised trusted cookie spec
- Re: FW: revised trusted cookie spec
Monday, 18 August 1997
- Re: FW: revised trusted cookie spec
- Re: commentURL, again.
- Re: FW: revised trusted cookie spec
- commentURL, again.
- Re: FW: revised trusted cookie spec
- Re: FW: revised trusted cookie spec
- "virtual connect-a-thon"
Friday, 15 August 1997
Thursday, 14 August 1997
Wednesday, 13 August 1997
Tuesday, 12 August 1997
- Re: RE-VERSION
- What is a "message version" (was Re: RE-VERSION)
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
Monday, 11 August 1997
- Re: RE-VERSION
- Q: Methods and Headers?
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: a positive "no thanks" to cookies?
- Re: RE-VERSION
- Re: a positive "no thanks" to cookies?
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: a positive "no thanks" to cookies?
- Re: a positive "no thanks" to cookies?
- Re: a positive "no thanks" to cookies?
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
Sunday, 10 August 1997
Monday, 11 August 1997
Sunday, 10 August 1997
- Re: RE-VERSION
- Re: a positive "no thanks" to cookies?
- Re: RE-VERSION
- a positive "no thanks" to cookies?
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
- RE: RE-VERSION
- Re: RE-VERSION
- Re: RE-VERSION
Saturday, 9 August 1997
- Re: RE-VERSION
- Re: RE-VERSION
- Re: Revised Agenda for Munich
- Revised Agenda for Munich
- Re: RE-VERSION
- Re: RE-VERSION
- response w/o content-length
- Re: Issues-list item "CACHING-CGI"
- Re: New Editorial issue MESSAGE-BODY
Friday, 8 August 1997
- inconsistent use of MAY & SHOULD in 14.36.2 Range Retrieval Requests
- Re: draft-ieft-http-options-00.txt
- Re: Comments on OPTIONS draft
- Re: RE-VERSION
- Re: Comments on OPTIONS draft
- Q:Which headers go with which Methods?
- Re: RE-VERSION
- Re: RE-VERSION
- Re: Removing CommentURL
- RE-VERSION
Thursday, 7 August 1997
- RE: State Management pre-draft - combinational requirement
- "Warning" in draft -08
- Re: draft-ieft-http-options-00.txt
- draft-ieft-http-options-00.txt
- Re: Comments on OPTIONS draft
- Re: Using Content-Encoding and Content-Disposition together
- Comments on OPTIONS draft
- Content-Disposition suggested text changes
- Re: http-digest-aa-rev-00.txt
- Re: Using Content-Encoding and Content-Disposition together
- Re: Using Content-Encoding and Content-Disposition together
- Administriva: http-wg mailing list and spammers
- Re: Using Content-Encoding and Content-Disposition together
- Re: Using Content-Encoding and Content-Disposition together
- Re: Using Content-Encoding and Content-Disposition together
- Re: http-digest-aa-rev-00.txt
- Re: http-digest-aa-rev-00.txt
- Re: http-digest-aa-rev-00.txt
- Re: Using Content-Encoding and Content-Disposition together
- Re: http-digest-aa-rev-00.txt
Wednesday, 6 August 1997
- Re: http-digest-aa-rev-00.txt
- Re: Agenda for Munich
- Re: http-digest-aa-rev-00.txt
- Re: Agenda for Munich
- Re: http-digest-aa-rev-00.txt
- Agenda for Munich
Tuesday, 5 August 1997
- I-D ACTION:draft-ietf-http-digest-aa-rev-00.txt
- Re: Using Content-Encoding and Content-Disposition together
- I-D ACTION:draft-ietf-http-options-01.txt
- RE: multipart/byteranges
- RE: Using Content-Encoding and Content-Disposition together
- RE: Using Content-Encoding and Content-Disposition together
- RE: multipart/byteranges
Monday, 4 August 1997
- Re: multipart/byteranges
- RE: multipart/byteranges
- Re: multipart/byteranges
- Re: agenda for Munich
- Re: multipart/byteranges
- multipart/byteranges
Saturday, 2 August 1997
- Re: Using Content-Encoding and Content-Disposition together
- I-D ACTION:draft-ietf-http-state-man-mec-03.txt,.ps
- spec-08-EBNF analysis
- Using Content-Encoding and Content-Disposition together
Friday, 1 August 1997
- Re: agenda for Munich
- Re: agenda for Munich
- Re: Implementation Experience Content Encoding
- Re: Implementation Experience Content Encoding
- Re: Implementation Experience Content Encoding
- Re: 301/302
- Re: Implementation Experience Content Encoding
- Re: Implementation Experience Content Encoding
- Re: Implementation Experience Content Encoding
- Re: 301/302
- Implementation Experience Content Encoding
- Re: agenda for Munich
- agenda for Munich
- Re: 301/302
- Re: 301/302
- Re: 301/302
- Re: 301/302
Thursday, 31 July 1997
- Re: Issue 1310_CACHE
- Re: 301/302
- RE: 301/302
- RE: 301/302
- Re: 301/302
- Re: HTTP-WG new charter milestones
- Re: HTTP-WG new charter milestones
- Draft 08 submitted to IETF ID editor.
- Re: HTTP-WG new charter milestones
- I-D ACTION: draft-ietf-http-options-00.txt
- HTTP-WG new charter milestones
- Re: 301/302
- Three new I-Ds re. URL i18n
- POST problem
- RE: Issue 1310_CACHE
Wednesday, 30 July 1997
- multipart/x-mixed-replace
- Re: The meaning of 301 (was Re: 301/302)
- Issue 1310_CACHE
- ISSUE: 403vs404
- Re: Updated proposal for OPTIONS issue
- Re: Case (in)sensitivity in (Non-)Compliance headers
- Re: Updated proposal for OPTIONS issue
- Re: Issues-list item "CACHING-CGI"
- Re: 301/302
- Re: The meaning of 301 (was Re: 301/302)
- Re: ISSUE VARY: Proposed wording
- Re: ISSUE VARY: Proposed wording
- Re: Issues-list item "CACHING-CGI"
- RE: 301/302
- Re: Issues-list item "CACHING-CGI"
- Re: 301/302
- Re: 301/302
- Re: Updated proposal for OPTIONS issue
- Re: Another try at OPTIONS
- The meaning of 301 (was Re: 301/302)
- Re: 301/302
- Case (in)sensitivity in (Non-)Compliance headers
- Re: New Editorial issue MESSAGE-BODY
- Re: 301/302
- Cutoff for Draft 08 of the HTTP/1.1 spec.
- New Editorial issue MESSAGE-BODY
- Re: 301/302
- Re: Issues-list item "CACHING-CGI"
- Re: Set-Cookie2: "additive" vs. "independent"
- Re: [Fwd: 301/302]
- Re: Feedback on: draft-cohen-http305306-02.txt
Tuesday, 29 July 1997
Wednesday, 30 July 1997
Tuesday, 29 July 1997
- Re: Issues-list item "CACHING-CGI"
- Re: 301/302
- Re: Set-Cookie2: "additive" vs. "independent"
- Re: Set-Cookie2: "additive" vs. "independent"
- Re: [Fwd: 301/302]
- Re: [Fwd: 301/302]
- RE: [Fwd: 301/302]
- Re: [Fwd: 301/302]
- [Fwd: 301/302]
- Re: 301/302
- Issues-list item "CACHING-CGI"
- Re: 301/302
- RE: 301/302
- Re: Set-Cookie2: "additive" vs. "independent"
- Re: Set-Cookie2: "additive" vs. "independent"
- Re: Set-Cookie2: "additive" vs. "independent"
- Re: Set-Cookie2: "additive" vs. "independent"
- Re: Set-Cookie2: "additive" vs. "independent"
- Re: Updated proposal for OPTIONS issue
- Re: an (unofficial) cookie draft
- I-D ACTION:draft-ietf-http-feature-reg-02.txt
- I-D ACTION:draft-ietf-http-feature-scenarios-01.txt
- I-D ACTION:draft-ietf-http-rvsa-v10-02.txt
- Set-Cookie2: "additive" vs. "independent"
- Re: 301/302
- IETF in Munich: 8/11 & 8/12
- Re: an (unofficial) cookie draft
- Re: Comment-URL question
Monday, 28 July 1997
- Re: Comment-URL question
- RE: 301/302
- Re: Comment-URL question
- Re: Comment-URL question
- I-D ACTION:draft-ietf-http-negotiation-03.txt (re-send)
- Re: Comment-URL question
- Issue CONTENT-ENCODING
- AUTH-CHUNKED proposed resolution
- New content negotiation drafts available
- Re: Comment-URL question
- Comment-URL question
- CACHING editorial issue...
- ISSUE: CHARSET DEFAULT
- Re: Removing CommentURL
- Re: Updated proposal for CONTENT-ENCODING issue
- LAST CALLs, closed issues, and new HTTP/1.1 draft
- Updated proposal for CONTENT-ENCODING issue
- Re: Removing CommentURL
- I-D ACTION:draft-ietf-http-negotiation-03.txt
- Streams connected to http responses?
- HTTP status codes (resent)
Sunday, 27 July 1997
- Re: Removing CommentURL
- Re: Removing CommentURL
- Re: Removing CommentURL
- Re: 301/302
- Re: Redirects
- Re: Removing CommentURL
- Re: State Management pre-draft - combinational requirement
- Re: Removing CommentURL
- Re: OPTIONS Spec
Saturday, 26 July 1997
- State Management pre-draft - combinational requirement
- Re: Removing CommentURL
- Re: Removing CommentURL
- Re: Removing CommentURL
- Re: Removing CommentURL
Friday, 25 July 1997
- RE: 301/302
- Re: Removing CommentURL
- 301/302
- Re: Removing CommentURL
- Re: New Issue REDIRECTS
- Re: Removing CommentURL
- an (unofficial) cookie draft
- RE: New Issue REDIRECTS
- RE: New Issue REDIRECTS
- Removing CommentURL
- RE: New Issue REDIRECTS
- Re: Updated proposal for CONTENT-ENCODING issue
- New Issue REDIRECTS
- RE: can't really be LAST CALL,"HTTP State Management Mechanism (Rev1) " to Propo
- Re: Updated proposal for OPTIONS issue
- Feedback on: draft-cohen-http305306-02.txt
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- 305/306 spec
- Updated proposal for OPTIONS issue
- Updated proposal for CONTENT-ENCODING issue
- HTTP and friends status codes
Thursday, 24 July 1997
- Re: CONTENT-ENCODING: FIXED revised proposed wording
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Proposed resolution for IDEMPOTENT issue
- Re: HTTP status codes
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: Another try at OPTIONS
- Re: CONTENT-ENCODING: FIXED revised proposed wording
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: I-D on RFC 2069 issue: digest request
- Re: Another try at OPTIONS
- Re: RETRY-AFTER HTTP working group issue...
- Additional LAST CALL issues
- Re: Another try at OPTIONS
- Re: Another try at OPTIONS
- Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: Another try at OPTIONS
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Wednesday, 23 July 1997
- Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: The significance of Cookies
- Re: HTTP status codes
- Re: HTTP status codes
- Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: HTTP status codes
- Re: The significance of Cookies
- Re: can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: CONTENT-ENCODING: FIXED revised proposed wording
- The significance of Cookies
- Re: HTTP status codes
- HTTP status codes
- can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: Another try at OPTIONS
- 1.1 proxies?
- Re: CONTENT-ENCODING: FIXED revised proposed wording
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- CONTENT-ENCODING: FIXED revised proposed wording
- CONTENT-ENCODING: revised proposed wording
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: 305/306
Tuesday, 22 July 1997
- Another try at OPTIONS
- Re: OPTIONS Spec
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Roy Fielding's comments on draft-ietf-http-hit-metering-03
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- I-D on RFC 2069 issue: digest request
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- SPEC 305/306
- OPTIONS Spec
- Proposed solution for issue CLARIFY-NO-CACHE
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Editorial ISSUE REMOVE_19.6
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
Monday, 21 July 1997
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Re: Any objections to "Accept-encoding: gzip, *;q=0"?
- Any objections to "Accept-encoding: gzip, *;q=0"?
- [Announce] PEP demo at w3c site
- Re: 305/306
- RANGE-ERROR: proposed solution
- Re: ISSUE: LANGUAGE-TAG
- Re: ISSUE CACHE-DIRECTIVE: What is the proposal?
- Editorial ISSUE REMOVE_19.6
- Re: ISSUE: LANGUAGE-TAG
- Q: HOWTO use different transmission schemes?
- Last Call: Simple Hit-Metering and Usage-Limiting for HTTP to Proposed Standard
Saturday, 19 July 1997
- Re: STATUS100 Re: Proposed resolution
- Re: draft-ietf-http-feature-reg-01.txt
- ISSUE CACHE-DIRECTIVE: What is the proposal?
- ISSUE QUOTED-BACK: What is the proposal?
- Re: New feature tag registration drafts available
- Re: draft-ietf-http-negotiation-02.txt
- Re: LAST CALL on MAX-AGE issue
- Re: ISSUE: LANGUAGE-TAG
- Re: ISSUE CONTENT-ENCODING: Proposed wording
- LAST CALL on MAX-AGE issue
- Re: STATUS100 Re: Proposed resolution
Friday, 18 July 1997
- Revised resolution for the STATUS100 issue
- Re: Proposed resolution for the STATUS100 issue
- Re: STATUS100 Re: Proposed resolution
- Re: ISSUE: LANGUAGE-TAG
- Re: STATUS100 Re: Proposed resolution
- Re: STATUS100 Re: Proposed resolution
- Re: Proposed resolution for the STATUS100 issue
- RE: Proposed resolution for the STATUS100 issue
- Re: ISSUE VARY: Proposed wording
- ISSUE: LANGUAGE-TAG
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: STATUS100 Re: Proposed resolution
- Re: Proposed resolution for the STATUS100 issue
- Re: Proposed resolution for the STATUS100 issue
- Re: STATUS100 Re: Proposed resolution
- Re: Proposed resolution for the STATUS100 issue
Thursday, 17 July 1997
- Re: Proposed resolution for the STATUS100 issue
- RE: Proposed resolution for the STATUS100 issue
- RE: Is 100-Continue hop-by-hop?
- Re: [URN] HTTP resolution protocol
- Re: STATUS100 Re: Proposed resolution
- Re: STATUS100 Re: Proposed resolution
- Re: [URN] HTTP resolution protocol
- Re: STATUS100 Re: Proposed resolution
- Re: Proposed resolution for the STATUS100 issue
- Re: STATUS100 Re: Proposed resolution
- Re: STATUS100 Re: Proposed resolution
- ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE VARY: Proposed wording
- Re: Summary of STATUS100 issue
- STATUS100 Re: Proposed resolution
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: Q: About transmission schemes ?
- Q: About transmission schemes ?
- Re: Proposed resolution for the STATUS100 issue
- STATUS100 Re: Proposed resolution
- exit
- 305/306
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- draft-ietf-http-hit-metering-03.txt
Wednesday, 16 July 1997
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- LAST CALL (and other status changes) on HTTP/1.1 issues
- Proposed resolution for the STATUS100 issue
- Request IESG action for draft-ietf-http-hit-metering-03.txt
- I-D ACTION:draft-ietf-http-pep-04.txt, .ps
- I-D ACTION:draft-ietf-http-negotiate-scenario-01.txt
- cache-busting doc as RFC ?
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Tuesday, 15 July 1997
- input on HTTP for the year 2000 working group
- New version of PEP specification available
- Re: draft-ietf-http-feature-reg-01.txt
- Re: New feature tag registration drafts available
- Re: draft-ietf-http-negotiation-02.txt
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Sunday, 13 July 1997
Monday, 14 July 1997
- Re: draft-ietf-http-feature-reg-01.txt
- Re: New feature tag registration drafts available
- Re: Content negotiation requirements
- Re: draft-ietf-http-negotiation-02.txt
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Saturday, 12 July 1997
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1)" to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard
- Re: Is 100-Continue hop-by-hop?
Friday, 11 July 1997
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard
- TSPECIALS: another nit
- cc:Mail Link to SMTP Undeliverable Message
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
- Re: New feature tag registration drafts available
- Re: Is 100-Continue hop-by-hop?
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard
- RE: Is 100-Continue hop-by-hop?
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
Thursday, 10 July 1997
- Re: Is 100-Continue hop-by-hop?
- Re: New feature tag registration drafts available
- Re: Is 100-Continue hop-by-hop?
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Re: Summary of STATUS100 issue
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE VARY: Proposed wording
- Re: ISSUE VARY: Proposed wording
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
- MUST and SHOULD, other kinds of proxies, and ISSUE PROXY-AUTHORIZATION
- Re: New feature tag registration drafts available
- Re: draft-ietf-http-feature-reg-01.txt
- Re: Summary of STATUS100 issue
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE VARY: Proposed wording
- Re: Is 100-Continue hop-by-hop?
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE VARY: Proposed wording
- Re: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
Wednesday, 9 July 1997
Thursday, 10 July 1997
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
- RE: Is 100-Continue hop-by-hop?
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
Wednesday, 9 July 1997
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo sed Standard
- Summary of STATUS100 issue
- Re: ISSUE CONTENT-ENCODING: Proposed wording
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Eleventh International Unicode Conference
Tuesday, 8 July 1997
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: HIT METERING to IESG on July 15
- Re: HIT METERING to IESG on July 15
- HIT METERING to IESG on July 15
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE CONTENT-LOCATION: Proposed wording
- Re: ISSUE VARY: Proposed wording
- Re: Refresh, non-standard headers, [was Re: Forcing to another page to load]
- Re: Refresh, non-standard headers, [was Re: Forcing to another page to load]
- Re: Refresh, non-standard headers
- Re: Refresh, non-standard headers, [was Re: Forcing to another page to load]
- Re-revised HTTP WG charter dates
- LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
- I-D ACTION:draft-ietf-http-feature-scenarios-00.txt
- I-D ACTION:draft-ietf-http-feature-reg-01.txt
- I-D ACTION:draft-ietf-http-hit-metering-03.txt
Monday, 7 July 1997
- Refresh, non-standard headers, [was Re: Forcing to another page to load]
- Is 100-Continue hop-by-hop?
- New feature tag registration drafts available
- Re: ISSUE VARY: Proposed wording
- Re: SAFE, UAHINT and other things not part of HTTP/1.1 now
- Re: SAFE, UAHINT and other things not part of HTTP/1.1 now
- Re: ISSUE VARY: Proposed wording
- Re: Content negotiation requirements
Sunday, 6 July 1997
Monday, 7 July 1997
Sunday, 6 July 1997
- Re: Forcing to another page to load
- Re: Forcing to another page to load
- Re: Forcing to another page to load
Wednesday, 2 July 1997
Friday, 4 July 1997
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: Proposal: 100-Continue optional under Client control
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: Proposal: 100-Continue optional under Client control
- Re: Proposal: 100-Continue optional under Client control
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: GET and referer security considerations
- Re: Proposal: 100-Continue optional under Client control
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: ISSUE CONTENT-ENCODING: Proposed wording
- Re: Revised HTTP WG charter dates
- Re: Content negotiation requirements
- Re: Interesting stats on the prevalence of bogus Last-Modified times
- Content negotiation requirements
- Re: feature registration expired
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- Re: GET and referer security considerations
- Interesting stats on the prevalence of bogus Last-Modified times
Thursday, 3 July 1997
- feature registration expired
- LAST CALL on four issues from http://www.w3.org/pub/WWW/Protocols/HTTP/Issues/
- Re: ISSUE CONTENT-ENCODING: Proposed wording
- Revised HTTP WG charter dates
- Re: ISSUE PROXY-AUTHORIZATION: Proposal wording
- ISSUE VARY: Proposed wording
- ISSUE PROXY-AUTHORIZATION: Proposal wording
- ISSUE CONTENT-LOCATION: Proposed wording
- ISSUE CONTENT-ENCODING: Proposed wording
- Re: draft-ietf-http-negotiation-02.txt
- Re: GET and referer security considerations
- Re: HTTP/1.1 & Proxies
- Re: GET and referer security considerations
Wednesday, 2 July 1997
- Re: GET and referer security considerations
- Re: Proposal: 100-Continue optional under Client control
- Re: Proposal: 100-Continue optional under Client control
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: Proposal: 100-Continue optional under Client control
- Re: GET and referer security considerations
- Re: GET and referer security considerations
- Re: GET and referer security considerations
- Re: GET and referer security considerations
- Re: GET and referer security considerations
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: GET and referer security considerations
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
- Re: HTTP/1.1 & Proxies
Tuesday, 1 July 1997
- Re: GET and referer security considerations
- Re: HTTP/1.1 & Proxies
- Re: GET and referer security considerations
- RE: HTTP/1.1 & Proxies
- Re: GET and referer security considerations
- Re: HTTP/1.1 & Proxies
- GET and referer security considerations
- Re: Assigned paths
- Re: Digest Authentication bleat
- Re: HTTP/1.1 & Proxies