HTTP-wg Archive by subject
Starting: Wed 01 Jan 1997 - 20:19:25 GMT
Ending: Mon 05 Jan 1998 - 13:50:17 GMT
Messages: 2787
- "DoubleClick Tries to Force Hand into Cookie Jar"
- "last call": draft-ietf-http-versions-01.txt
- "versions" -> Informational RFC
- "virtual connect-a-thon"
- "Warning" in draft -08
- "Warning" in draft -08 (WARNING)
- $$$ Advertise Your Business Globally ??
- (=?EUC-KR?B?waa48Q==?= =?EUC-KR?B?vvjAvQ==?=)
- (Fwd) web-priv list set up
- (no subject)
- (revised) Minutes, HTTP Working Group, Munich IETF Aug 11-12
- 1.1 proxies?
- 1.1 server available for testing
- 16" Cheese Pizza $3.40
- 19.9 requirements summary
- 1xx Clarification
- 1xx Clarification)
- 24 Hour CASH Grab is on-.
- 301/302
- 301/302)
- 305 Use proxy
- 305/306
- 305/306 response codes
- 305/306 spec
- 500+Search Engines.
- [Announce] PEP demo at w3c site
- [Fwd: 301/302]
- [Fwd: I-D ACTION:draft-lyon-itp-nodes-02.txt]
- [Fwd: LAST CALL: draft-ietf-http-state-man-mec-04.txt]
- [Fwd: RFC 2183 on Content-Disposition]
- [Fwd: SEC - Protocol names for security protocols]
- [Fwd: WEBPRIV BOF for D.C. IETF]
- [URN] HTTP resolution protocol
- A broken browser
- A common registry for MIME headers?
- A linguistic note on unverifiable transactions
- A new suggestion on 100 CONTINUE
- a positive "no thanks" to cookies?
- Accept header and inline images
- Accept-Language prefix matching (was: A broken browser)
- Accept-Ranges
- Accept-Transfer header field (was HTTP/1.1 Issues:
- Accept-Transfer header field (was HTTP/1.1 Issues: TRAILER_FIELDS)
- Access control and knowledge
- Acknowledgements for Draft standard...
- Additional LAST CALL issues
- Administriva: http-wg mailing list and spammers
- Administrivia: getting off this list
- Administrivia: http-wg mailing list outage
- Administrivia: running on automatic
- Administrivia: spam reduction
- Administrvia: list status
- Adminstrivia: spam reduction
- Advertisement: Web Site Hosting
- Advertisement: Website Hosting
- Advertisment: Web Hosting
- Age calculation in HTTP: two Internet Drafts
- Age Header Field in HTTP/1.1
- Agenda for HTTP working group April 7
- Agenda for Munich
- Agenda for WEBPRIV BOF, Mon Dec 8 1930-2200
- agenda, HTTP working group, 40th IETF
- Alternate HTTP-WG mailing list: ietf-http-wg@w3.org
- Alternates?
- an (unofficial) cookie draft
- An experiment in producing RFC1122-style requirements checklist
- Announcement: A new Wiley book on World Wide Web Security
- announcing: http-state mailing list
- Another Question on byte ranges
- Another try at OPTIONS
- Another way to pipeline cache validation....
- Any objections to "Accept-encoding: gzip, *;q=0"?
- Apache and HTTP/1.1
- Apache Group
- Apache Groupy
- Aplogize (was Bulletin news)
- Assigned paths
- AUTH-CHUNKED proposed resolution
- Authentication-Info in Chunked Footer
- Authorization draft: Authentication-Info syntax
- Back from the grave: Unverifiable Transactions and Cookies
- Basic Authentication behavior
- Basic Authentication behavior (last call on PROTECTION_SPACES)
- Basic Authentication behavior (PROTECTION_SPACE issue.)
- Benefits Managers \ Administrators
- Buggy TCP implementations. Was: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- byte range questions
- cache-busting and charsets again
- cache-busting doc as RFC ?
- cache-busting document
- Cache-Control directive, semantics
- Cache-control: private and off-line
- Cache-control: proxy-maxage as MUST for HTTP/1.1?
- Cacheing encrypted objects
- CACHING editorial issue...
- Calculation of age headers
- Calculation of age headers (AGE-CALCULATION last call)
- Calendaring Interoperability over HTTP
- Call for Closure - HTTP response version
- Call for Closure - HTTP response version
- Call for comments on feature tag syntax
- Call for Papers - 11th Unicode Conference - September 1997, California
- Can I add a link to your site from mine?
- can't really be LAST CALL,
- can't really be LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- Case (in)sensitivity in (Non-)Compliance headers
- Caught you in the act....
- cc:Mail Link to SMTP Undeliverable Message
- Change to Chunk Length Syntax
- Changes to the spec
- charsets again
- Claification requested in Host:
- Claification requested in Host: (HOST issue proposed wording.)
- Clock skew and the importance of clock synchronization in HTTP servers.
- Code 419 should have been 417 (editorial issue CODES)
- Comment on PEP draft
- Comment-URL question
- COMMENT: LAST CALL comment
- COMMENT: resolution
- Comments on I-D ACTION:draft-ietf-http-options-02.txt
- Comments on draft-ietf-http-hit-metering-00.txt
- Comments on draft-ietf-http-negotiation-00.txt
- comments on draft-ietf-http-state-man-mec-04.txt
- Comments on draft-mogul-http-hit-metering-00.txt
- Comments on draft-mogul-http-hit-metering-01.txt
- comments on http-authentication-00
- comments on jaye-trust-state-01
- Comments on OPTIONS draft
- Comments on PEP draft
- Comments on the new cookie draft
- commentURL, again.
- Common Gateway Interface
- Compressing HTML
- confidentiality and the referer field
- Confused about persistent connection for old clients
- Content encoding problem...
- Content negotiation requirements
- Content negotiation, features, and related items
- Content ranges in HTTP/1.1
- Content-Base bugs in User Agents
- Content-Coding on POST
- Content-Disposition suggested text changes
- CONTENT-ENCODING: FIXED revised proposed wording
- CONTENT-ENCODING: revised proposed wording
- Content-Location in HTTP/1.1 text
- Content-Range and Caching Proxies
- Cookie domain
- cookie draft
- cookie Port summary
- Cookie Question
- cookies
- cookies -- by the way
- Cookies and cache
- cookies and security
- Cookies in the news
- cookies: 2/4 headers?
- copyright issues for proxy caches and archival services
- CREATE MULTIPLE STREAMS OF INCOME!!!
- Customizing the authentication dialog
- Cutoff for Draft 08 of the HTTP/1.1 spec.
- Daily News Bulletin
- DATE-IF-MODIFIED
- Date/time on the Internet
- DAV Searching and Locating Mini-BOF
- deflate
- DES attack, help crack bad encryption!
- determining proxy reliability
- Digest Authentication bleat
- Digest Authentication, Netscape, and Microsoft
- Digest mess
- Document Action: Use and interpretation of HTTP version numbers to
- doubt
- draft '08' => draft-ietf-http-v11-spec-rev-00.*
- Draft 08 submitted to IETF ID editor.
- DRAFT agenda for IETF meeting; documenting implementations
- DRAFT Minutes, HTTP Working Group, Munich IETF
- draft minutes, HTTP-WG meetings April
- draft minutes, HTTP-WG meetings April 7
- draft minutes, HTTP-WG meetings April 7)
- Draft standard rules (was RE: What is Content-Length?)
- draft-daviel-metadata-link-00.txt
- draft-fielding-url-syntax-08 issue
- draft-holtman-http-safe-01.txt
- draft-holtman-http-safe-01.txt]
- draft-ieft-http-options-00.txt
- draft-ietf-http-feature-reg-01.txt
- draft-ietf-http-hit-metering-03.txt
- draft-ietf-http-negotiate-scenario.00.txt
- draft-ietf-http-negotiation-02.txt
- draft-ietf-http-req-sum-00.txt
- draft-ietf-http-state-man-mec-01 submitted
- draft-ietf-http-state-man-mec-03: $Version and path
- draft-ietf-http-state-man-mec-04.txt
- draft-ietf-http-versions-00.txt
- draft-lundblade-1pass-mult-alt-00.txt vs. alternates
- draft-mogul-http-revalidate-00.txt
- EARN EXTRA HOLIDAY CASH!!
- Economics of Electronic Commerce: New Book Announcement
- editorial glitch in section 14.19
- Editorial ISSUE REMOVE_19.6
- Editorial Nit in section 4.1 (new editorial issue GENERIC_MESSAGE)
- Editorial suggestion to change Request-URI to Request-Target
- Eleventh International Unicode Conference
- Enough spam
- errata for cookie spec
- Erratum for draft-ietf-http-negotiation-00.txt
- Existance of Proxies that Add Headers
- exit
- extensibility of status codes (was: 301/302)
- Fact-checking: do any in-service proxy caches ever ignore
- Fact-checking: do any in-service proxy caches ever ignore Expires?
- Fbk on state-man-mec-04.txt
- Feature negotiation requirements
- feature negotiation syntax
- feature registration expired
- Feedback on: draft-cohen-http305306-02.txt
- FindMail Archive
- First draft of negotiation requirements document
- Forcing to another page to load
- Forcing to another page to load]
- FREE ADVICE BY MASTER PSYCHIC / FREE CALL
- FREE Info - fANTASTIC *CA$H* INTERNET HOMEBIZ
- FREE LISTING in Worldwide Directory
- Free offer from Oasis Casino and Sportsbook !!
- FREE PUTTER!
- Free Software
- FREE SOFTWARE !!!
- from the AD: content-length is invalid within multipart
- ftp URL stuff (was MIME multipart/* vs HTTP)
- FTP urls
- FW: Proposed amendment to RFC2109
- FW: revised trusted cookie spec
- Fwd: Announcing Connectathon '98
- FYI [Internet-Drafts@ietf.org: I-D ACTION:draft-pohlmann-http-traffic-satellite-00.txt]
- FYI: New IETF WEBDAV Working Group
- Genuine Oil Portraits From Photos
- GET and referer security considerations
- Getting Pedro off this list...
- Globally unique e-tags, if-match on content-ID, etc.
- good words for HTTP interoperability testing
- Graham Klyne on content negotiation
- GREAT Information about CREDIT!! *!
- Head response Transfer-Encoding: chunked?
- Hello!
- HIT METERING to IESG on July 15
- hit metering: wait until next draft?
- Hit-meter draft (was Unidentified subject!)
- Hit-metering implementations
- Hold your cookie-talk
- Hostile webserver attack!!!!
- HOT Email Address Now !!
- How to add new "protocols" ?
- How to get MORE RECRUITS for YOUR PROGRAM!
- HTML "include": see WD-object [was: HTTP Connection Management]
- HTTP
- HTTP 1.1 Issue: 403VS404
- HTTP 1.1 Issue: When To Close Connections
- HTTP and friends status codes
- http compression
- HTTP Connection Management (draft-ietf-http-connection-00.txt)
- HTTP Connection Management(draft-ietf-http-connection-00.txt))
- HTTP Connection Management(draft-ietf-http-connection-00.txt)01BC4370.78DF0090@crecy.ai.mit.edu
- HTTP Download
- HTTP events at www6 conference?
- HTTP Interoperability Test 10-30
- HTTP Interoperability Test 11-13 (correct date)
- HTTP Interoperability Test 12-4
- HTTP Issues LAST CALL; HTTP editing group
- HTTP POST and Cookies
- HTTP practice and Year-2000: the bad(?) news
- HTTP question.
- HTTP response version, again
- HTTP State Management Mechanism (Rev1): EndSession attribute
- HTTP status codes
- HTTP status codes (resent)
- HTTP tutorial online (1.0 and 1.1)
- HTTP version number for 1.1 -> 1.0 responses
- HTTP WG status, scheduling
- HTTP working group status; VOLUNTEERS needed
- http-digest-aa-rev-00.txt
- http-equiv and new http headers
- http-ext wg mailing list ready
- HTTP-WG new charter milestones
- HTTP-WG recommends "SAFE" and "UAHINT" for "Experimental"
- HTTP/1.1 & Proxies
- HTTP/1.1 (RFC 2068) wording nit
- HTTP/1.1 - Retry-after for 3xx as well as 503?
- HTTP/1.1 -- who disconnects the session?
- HTTP/1.1 draft rev-01 and authentication draft 00 issued....
- HTTP/1.1 in the news
- HTTP/1.1 Issue: max-age in responses not defined
- HTTP/1.1 Issue: max-age in responses not defined
- HTTP/1.1 issue: Proxy-Authorization
- HTTP/1.1 ISSUE: TRAILER_FIELDS - Proposed Resolution
- HTTP/1.1 Issues list
- HTTP/1.1 Pipelining
- I'm starting draft production right now...
- I-D ACTION: draft-ietf-http-options-00.txt
- I-D ACTION:draft-cohen-http-305-306-responses-00.txt
- I-D ACTION:draft-holtman-http-safe-03.txt (fwd)
- I-D ACTION:draft-http-hit-metering-00.txt
- I-D ACTION:draft-ietf-http-alternates-00.txt
- I-D ACTION:draft-ietf-http-authentication-00.txt
- I-D ACTION:draft-ietf-http-connection-00.txt
- I-D ACTION:draft-ietf-http-digest-aa-rev-00.txt
- I-D ACTION:draft-ietf-http-feature-reg-01.txt
- I-D ACTION:draft-ietf-http-feature-reg-02.txt
- I-D ACTION:draft-ietf-http-feature-scenarios-00.txt
- I-D ACTION:draft-ietf-http-feature-scenarios-01.txt
- I-D ACTION:draft-ietf-http-hit-metering-00.txt
- I-D ACTION:draft-ietf-http-hit-metering-01.txt
- I-D ACTION:draft-ietf-http-hit-metering-02.txt
- I-D ACTION:draft-ietf-http-hit-metering-03.txt
- I-D ACTION:draft-ietf-http-hit-metering-04.txt
- I-D ACTION:draft-ietf-http-jaye-trust-state-00.txt
- I-D ACTION:draft-ietf-http-jaye-trust-state-01.txt
- I-D ACTION:draft-ietf-http-negotiate-scenario-00.txt
- I-D ACTION:draft-ietf-http-negotiate-scenario-01.txt
- I-D ACTION:draft-ietf-http-negotiate-scenario-02.txt
- I-D ACTION:draft-ietf-http-negotiation-00.txt
- I-D ACTION:draft-ietf-http-negotiation-01.txt
- I-D ACTION:draft-ietf-http-negotiation-02.txt
- I-D ACTION:draft-ietf-http-negotiation-03.txt
- I-D ACTION:draft-ietf-http-negotiation-03.txt (re-send)
- I-D ACTION:draft-ietf-http-negotiation-04.txt
- I-D ACTION:draft-ietf-http-options-01.txt
- I-D ACTION:draft-ietf-http-options-02.txt
- I-D ACTION:draft-ietf-http-pep-01.txt
- I-D ACTION:draft-ietf-http-pep-02.txt
- I-D ACTION:draft-ietf-http-pep-03.txt
- I-D ACTION:draft-ietf-http-pep-04.txt, .ps
- I-D ACTION:draft-ietf-http-pep-05.txt
- I-D ACTION:draft-ietf-http-req-sum-00.txt
- I-D ACTION:draft-ietf-http-rvsa-v10-01.txt
- I-D ACTION:draft-ietf-http-rvsa-v10-02.txt
- I-D ACTION:draft-ietf-http-state-man-mec-00.txt, .ps
- I-D ACTION:draft-ietf-http-state-man-mec-01.txt, .ps
- I-D ACTION:draft-ietf-http-state-man-mec-02.txt, .ps
- I-D ACTION:draft-ietf-http-state-man-mec-03.txt,.ps
- I-D ACTION:draft-ietf-http-state-man-mec-05.txt,.ps
- I-D ACTION:draft-ietf-http-state-mgmt-errata-00.txt, .ps
- I-D ACTION:draft-ietf-http-uahint-00.txt
- I-D ACTION:draft-ietf-http-uahint-01.txt
- I-D ACTION:draft-ietf-http-v11-spec-rev-00.txt
- I-D ACTION:draft-ietf-http-v11-spec-rev-01.txt
- I-D ACTION:draft-ietf-http-versions-00.txt
- I-D ACTION:draft-ietf-http-versions-01.txt
- I-D ACTION:draft-mogul-http-revalidate-00.txt
- I-D on RFC 2069 issue: digest request
- ID: Proxy autoconfig
- ID: Proxy autoconfig
- ID: wildcards in Accept-Charset
- IETF HTTP-WG agenda
- IETF in Munich: 8/11 & 8/12
- If-None-Match and IMS (new Issue IMS_INM_MISMATCH)
- Ignore proxy
- Implementation Experience Content Encoding
- inconsistent use of MAY & SHOULD in 14.36.2 Range Retrieval Requests
- Inconsistent wording of Content-Length
- indefinite server-push (was 'Last-Modified in chunked footer')
- Indexing non-HTML objects
- input on HTTP for the year 2000 working group
- Insisting on a message digest (rfc2069)
- Interest in standard HTTP headers for specifying client
- Interest in standard HTTP headers for specifying client display attributes?
- Interesting stats on the prevalence of bogus Last-Modified times
- Internet Draft http-versions-00
- Internetowa Ksiazka Teleadresowa
- Interoperability Event
- Interoperability Test 10-16
- Interoperability Test 10-23
- Interoperability Test Survey
- Interoperability Test Survey (updated)
- IPP> MIME multipart/* vs HTTP
- IPP>PRO - http comments
- Is 100-Continue hop-by-hop?
- Is MHTML only for e-mail?
- Is Your Web Site A Secret?
- Issue 1310_CACHE
- ISSUE CACHE-DIRECTIVE: What is the proposal?
- Issue CONTENT-ENCODING
- ISSUE CONTENT-ENCODING: Proposed wording
- ISSUE CONTENT-LOCATION: Proposed wording
- ISSUE PROXY-AUTHORIZATION: Proposal wording
- ISSUE QUOTED-BACK: What is the proposal?
- Issue SAFE
- ISSUE VARY: Proposed wording
- Issue: 304-LAST-MODIFIED (Should 304 include Last Modified?)
- ISSUE: 403vs404
- Issue: BYTE-RANGE (Is the right meta-data returned on range
- Issue: BYTE-RANGE -- resolved?
- ISSUE: CHARSET DEFAULT
- ISSUE: LANGUAGE-TAG
- ISSUE: MUST a client wait for 100 when doing PUT or POST
- ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- ISSUE: MUST a client wait for 100 when doing PUT or POST re
- ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- Issue: TRAILER_FIELDS and Transfer Encodings last time...
- Issue: TRAILER_FIELDS and Transfer Encodings once again
- Issues list updated to reflect Monday session at the IETF in
- Issues with the cookie draft
- Issues-list item "CACHING-CGI"
- Issues-list item "DISPOSITION"
- Issues-list item "LWS-DELIMITER"
- Issues-list item "QZERO"
- It's Back!!!!
- LAST CALL (and other status changes) on HTTP/1.1 issues
- LAST CALL on four issues from http://www.w3.org/pub/WWW/Protocols/HTTP/Issues/
- LAST CALL on issues; status
- LAST CALL on MAX-AGE issue
- LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
- LAST CALL, "HTTP State Management Mechanism (Rev1)" to Propo
- LAST CALL: draft-ietf-http-state-man-mec-04.txt
- Last Call: Simple Hit-Metering and Usage-Limiting for HTTP to
- LAST CALLs, closed issues, and new HTTP/1.1 draft
- Last-Modified in chunked footer
- LWS in quoted-string
- LYNX-DEV two curiosities from IETF
- LYNX-DEV two curiosities from IETF HTTP session.
- Mail Order Business-NOT MLM
- mailto:http-wg@cuckoo.hpl.hp.com
- making progress on cookies
- Memphis followup
- Memphis followup)
- Memphis scheduling
- Metadata proliferation
- mid-course errors
- MIME multipart/* vs HTTP
- minimal OPTIONS
- Minutes from HTTP/1.1 Implementor's dinner
- Minutes from Second HTTP session at IETF-40
- more on digest (was: Unidentified subject!)
- More thoughts on content negotiation
- multipart/byteranges
- multipart/x-mixed-replace
- MUST a client wait for 100 when doing PUT or POST?
- MUST and SHOULD, other kinds of proxies, and ISSUE PROXY-AUTHORIZATION
- My Loss is YOUR GAIN!!!
- Need HTTP proxy source
- Negotiation comments
- Netscape Server security question...
- Netscape's Marc Andreessen on Unicode + the Web
- Network Performance Effects of HTTP/1.1, CSS1, and PNG
- New content negotiation draft available
- New content negotiation draft: draft-ietf-http-negotiation-02.txt
- New content negotiation drafts available
- new cookie draft
- new cookie I-D submitted
- New Editorial issue MESSAGE-BODY
- new editorial issue RANGE_WITH_CONTENTCODING
- New feature negotiation syntax
- New feature tag registration drafts available
- New I-D for Http Jaye Trust State Mgt
- New Issue REDIRECTS
- New Issue: Incompatiblity between caching needs and persistant connections.
- New mailing list on 'content negotiation'
- New PEP draft available as ID!
- New Proposed Chunked Rules
- new prospective cookie draft
- New version of PEP specification available
- no one supports Digest
- notes from previous Editing Group meeting: goals, docking
- Now available: extensive HTTP proxy traces from DECWRL
- NUDGE: Our piece on Host: and URLs (Fwd)
- On CommentURSs ....
- OPS specification
- OPTIONS method
- OPTIONS Spec
- Oracle Web Server 3.0 with SSL
- origin server vs. proxy with full URL
- Origin Servers without Clocks
- Padding size in chunked encoding
- Parameters for transfer-codings?
- PEP and new methods
- PEP draft 5 (21 Nov 1997)
- PEP draft delayed -- diffs so far attached
- PEP draft for review
- PEP draft for review]
- PEP Integration in RTSP
- Persistent connections, and 1.0 browsers
- Persistent connections: current implementations?
- Pipelining and compression effect on HTTP/1.1 proxies
- pipelining vs. deferred content
- Please clarify * is legal in HTTP1/1 Accept-Charset Header
- Please remove from this mailing list asap.
- POST
- POST +
- POST problem
- privacy platforms
- problems with cookies
- Process for closing out issues list
- Program Makes Believers Of Skeptics!
- Proposal for new HTTP 1.1 authentication scheme
- Proposal for Weekly Internet HTTP/1.1 Tests
- Proposal: 100-Continue optional under Client control
- Proposal: Vary on Cookies
- Proposed amendment to RFC2109
- Proposed resolution
- Proposed resolution for IDEMPOTENT issue
- Proposed resolution for the STATUS100 issue
- Proposed solution for issue CLARIFY-NO-CACHE
- Proposed Standard for Alternates header
- Protocol Action: Simple Hit-Metering and Usage-Limiting for HTTP
- Proxy
- proxy autoconfiguration
- Proxy Keep-Alive
- proxy-cookie
- PROXY-REDIRECT status...
- PUT multipart
- PUT with Content-Range
- Q re draft 08's Accept-Encoding
- Q: About transmission schemes ?
- Q: HOWTO use different transmission schemes?
- Q: Methods and Headers?
- Q: protocolls and fault tolerance
- Q:Which headers go with which Methods?
- Quality factors
- Question
- Question about HTTP/1.1 and proxy servers
- question in French
- question on 14.9.4, no-cache directive in requests
- Question on Accept-Charset
- Question on byte ranges
- Question...
- Questions on draft-ietf-http-negotiation-00.txt
- Qvalues - a nit
- Random http-wg statistics
- RANGE-ERROR issue: proposed resolution
- RANGE-ERROR: proposed solution
- RANGE_WITH_CONTENTCODING
- RANGES (Might be nice to allow 206 response to range request
- Re-revised agenda for IETF HTTP meetings, Dec 8 & 10
- Re-revised HTTP WG charter dates
- RE-VERSION
- RE-VERSION discussion at Munich....
- RE-VERSION)
- RE: 1xx Clarification
- RE: 301/302
- RE: 305 Use proxy
- RE: 305/306 response codes
- RE: [Fwd: 301/302]
- RE: Advertisement: Web Site Hosting
- RE: An experiment in producing RFC1122-style requirements checkli
- RE: Apache Group
- RE: Apache Groupy
- RE: Call for Closure - HTTP response version
- RE: can't really be LAST CALL,"HTTP State Management Mechanism (Rev1) " to Propo
- RE: Comments on I-D ACTION:draft-ietf-http-options-02.txt
- RE: comments on http-authentication-00
- RE: comments on jaye-trust-state-01
- RE: Comments on the new cookie draft
- RE: Compressing HTML
- RE: confidentiality and the referer field
- RE: Content encoding problem...
- RE: cookie Port summary
- RE: Cookies and cache
- RE: Digest Authentication bleat
- RE: Digest Authentication, Netscape, and Microsoft
- RE: Digest mess
- RE: doubt
- RE: draft-ietf-http-req-sum-00.txt
- RE: e-mail
- RE: Editorial suggestion to change Request-URI to Request-Target
- RE: Enough spam
- RE: FW: revised trusted cookie spec
- RE: Getting Pedro off this list...
- RE: Globally unique e-tags, if-match on content-ID, etc.
- RE: Head response Transfer-Encoding: chunked?
- RE: HTTP State Management Mechanism (Rev1): EndSession attribute
- RE: HTTP/1.1 & Proxies
- RE: ID: Proxy autoconfig
- RE: ID: Proxy autoconfig
- RE: If-None-Match and IMS (new Issue IMS_INM_MISMATCH)
- RE: indefinite server-push (was 'Last-Modified in chunked footer'
- RE: indefinite server-push (was 'Last-Modified in chunked footer')
- RE: Indexing non-HTML objects
- RE: Is 100-Continue hop-by-hop?
- RE: Issue 1310_CACHE
- RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re
- RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
- RE: ISSUE: MUST a client wait for 100 when doing PUT or POST re quests?
- RE: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- RE: Issues with the cookie draft
- RE: Issues-list item "CACHING-CGI"
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Propo
- RE: LAST CALL, "HTTP State Management Mechanism (Rev1) " to Proposed Standard
- RE: Last-Modified in chunked footer
- RE: LYNX-DEV two curiosities from IETF HTTP session.
- RE: making no progress on cookies
- RE: making progress on cookies
- RE: mid-course errors
- RE: MIME multipart/* vs HTTP
- RE: Minutes from HTTP/1.1 Implementor's dinner
- RE: more on digest (was: Unidentified subject!)
- RE: multipart/byteranges
- RE: MUST a client wait for 100 when doing PUT or POST?
- RE: new cookie draft
- RE: new editorial issue RANGE_WITH_CONTENTCODING
- RE: New feature negotiation syntax
- RE: New I-D for Http Jaye Trust State Mgt
- RE: New Issue REDIRECTS
- RE: New PEP draft available as ID!
- RE: Padding size in chunked encoding
- RE: PEP draft delayed -- diffs so far attached
- RE: PEP Integration in RTSP
- RE: Pipelining and compression effect on HTTP/1.1 proxies
- RE: POST
- RE: Proposal for new HTTP 1.1 authentication scheme
- RE: Proposed resolution for the STATUS100 issue
- RE: RE-VERSION
- RE: RE-VERSION discussion at Munich....
- RE: REAUTHENTICATION REQUIRED
- RE: RFC2109 addition...
- RE: Section 10.1.1 Combining Set-Cookie and Set-Cookie2
- RE: Should server beable to say NoCookie, No Show?
- RE: spec-08 self-contradiction in 13.5.2
- RE: SSL Tunneling; Informational RFC; Last call?
- RE: State Management pre-draft - combinational requirement
- RE: The state of cookies
- RE: This is not "this is not a date"
- RE: Unverifiable Transactions / Cookie draft
- RE: Unverifiable Transactions / Cookie draft (Warning: Rant Enclo
- RE: URI or URL? [was: PEP draft delayed -- diffs so far attached]
- RE: Using Content-Encoding and Content-Disposition together
- RE: Using of Connection header
- RE: What is Content-Length?
- Re[2]: errata for cookie spec
- Re[2]: Unverifiable Transactions / Cookie draft
- REAUTHENTICATION REQUIRED
- Receive Free copy of the Home Business Journal
- Redirects
- references to obsolete RFC1522
- Refresh, non-standard headers
- Regarding Authentication
- remove
- Removing CommentURL
- req-sum-00
- Request for HTML Draft to support Multi Direction languages.
- Request for Input and Progress on PEP draft
- request for input of managing WWW-servers.
- Request IESG action for draft-ietf-http-hit-metering-03.txt
- response w/o content-length
- RETRY-AFTER HTTP working group issue...
- Returned mail: Host unknown (Name server: ucbvax.berkeley.edu: host not found) (fwd)
- Revised agenda for HTTP-WG, Dec 8, 1300-1500
- Revised Agenda for Munich
- Revised charter ,
- Revised charter , milestones
- Revised charter ,milestones
- Revised charter milestones
- Revised HTTP WG charter dates
- Revised HTTP-WG agenda for April 7
- revised HTTP-WG charter
- Revised http://www.w3.org/Protocols/HTTP/Issues/
- Revised resolution for the STATUS100 issue
- Revised S-HTTP draft
- Revised UA HINT Draft Submitted
- Rewrite of feature tag syntax rules
- RFC 2068 and 2069!
- RFC 2109 on HTTP State Management Mechanism
- RFC2109 addition...
- Roy Fielding's comments on draft-ietf-http-hit-metering-03
- Safe header -> experimental RFC
- SAFE, UAHINT and other things not part of HTTP/1.1 now
- schulzrinne-http-status-00.txt: three digits not enough
- Search Engine Secrets
- Secret 'Members Only' Site !
- Section 10.1.1 Combining Set-Cookie and Set-Cookie2
- Secure cookies survey
- Semantics of Content-Range in the PUT method
- Set-Cookie2: "additive" vs. "independent"
- Short report, HTTP WG meeting
- Should server beable to say NoCookie, No Show?
- SHOULD we include charset=ISO-8859-1?
- Slight wording error in section 13.5.4
- Snow Warning Service from AccuWeather
- Some edits to draft-ietf-http-negotiation-00.txt
- Some issues for the list
- some thoughts on extensions on REQUEST line.
- some thoughts on extensions on REQUEST line.
- sorry,i want to exit .
- SPEC 305/306
- spec-08 self-contradiction in 13.5.2
- spec-08-EBNF analysis
- Spelling of "cachable"
- spoofing cookies
- SSL tunneling status
- SSL Tunneling; Informational RFC; Last call?
- Start Saving Now...
- State management
- State Management pre-draft - combinational requirement
- State Mgmt/RFC 2109 plans
- State of draft Rev 01 (and digest rev 00)
- Status 100
- Streams connected to http responses?
- Submissions of both HTTP/1.1 and Authentication drafts...
- Suggestion: Add Cache-Control extensibility to Vary header
- Summary of STATUS100 issue
- Summary, HTTP-WG meeting in Memphis
- Syntax (and other) problems in Digest spec
- System management of HTTP clients
- Take All Men Look at this It's Cool !!!
- TCP spoofing
- tcpdump
- Ted Hardie's comments on draft-mogul-http-hit-metering-01.txt
- Tenth Int'l Unicode Conference - March 1997
- Test Day Schedule
- Testing 12-18
- testing......
- The 'Secret Members Only' Site!
- The problem with proxy-revalidate, and a proposed solution
- The significance of Cookies
- The state of cookies
- the state of State
- This is not "this is not a date"
- This message is never sent unsolicited.
- Three new I-Ds re. URL i18n
- Transient content negotiation
- Translated IUC10 Web pages: Experimental Results
- Transparent content negotiation pointers & status
- TSPECIALS: another nit
- Two Internet Drafts => Experimental RFCs
- UA Hint Proposal ... Interim Draft
- Unicode Conference - Final Reminder
- Unicode Conference - March 1997 - Reminder
- Unidentified subject!
- unverifiable transactions (was: Unidentified subject!)
- Unverifiable Transactions / Cookie draft
- Unverifiable Transactions / Cookie draft (Warning: Rant Enclo sed)
- Unverifiable Transactions / Cookie draft (Warning: Rant Enclosed)
- Updated Issues list...
- Updated proposal for CONTENT-ENCODING issue
- Updated proposal for OPTIONS issue
- Updated test implementation for TCN available
- URI -> URL when talking about 'moved ...'
- URI or URL? [was: PEP draft delayed -- diffs so far attached]
- Using Content-Encoding and Content-Disposition together
- Using of Connection header
- Vary and server parsed documents
- Want Your Business To EXPLODE This Weekend??
- Warnings, RFC 1522, and ISO-8859-1
- Washington Agenda for HTTP?
- web login session transfer?
- Web pages in twenty languages + Unicode
- Web Security
- Web Site Visibility
- WEB->FAX
- WebDAV-specific status codes
- webmaster@website
- Weekly Internet HTTP/1.1 Tests
- welcome back, you only missed "Digest mess"
- WG Last Call for draft-schulzrinne-http-status-00.txt
- What is Content-Length?
- What is the basic idea behind 305 Use Proxy?
- What method for Location?
- Whats servlets for?
- Wording to close out REDIRECTS issue.
- Work at HOME: Email Processors Needed....
- Your Free Listing in Government Purchasing Directory
- your mail
- your mail )
Last message date: Mon 05 Jan 1998 - 13:50:17 GMT
Archived on: Mon Jan 05 1998 - 14:05:54 GMT
This archive was generated by hypermail 1.02.