HTTP-WG Mailing List Archive for 2000 by subject
Starting: Tue 06 Jan 1970 - 06:42:24 PST
Ending: Tue 08 Dec 1970 - 06:53:52 PST
Messages: 325
- "Via" header field
- 1.1 proxy interaction with 1.0 client and bad EOF behavior
- 100% SPAM FREE email marketing works!
- [Fwd: Last Call: Use of HTTP State Management to BCP]
- [Fwd: Protocol Action: Use of HTTP State Management to BCP]
- [Fwd: RFC 2965 on HTTP State Management Mechanism]
- A Typical HTTP Problem
- Adminstrivia: spam fix
- Adworks 2 for 1 special promotion!
- Adworks Buy One Solo, Get one Free!
- ANN: HTTP compliance mailing list
- Another erratum for RFC2616
- Another revision of the I-D on "Delta encoding in HTTP"
- Browser support for request pipelining
- Cache-Control
- Caching Problem with 1.0 and a Proxy Server
- caching problems
- Chunked sample message
- Combining multiple message-header fields
- Conformance Test for HTTP 1.1
- Content-Encoding: gzip AND Content-Type:
- Content-Encoding: gzip AND Content-Type: application/x-javascript
- Content-Encoding: gzip AND Content-Type:application/x-javascript
- Cookie problem with IE5 and Windows 2000
- cookies patent
- CRLF on POST requests, where/how
- CRLF on POST requests, where/how specified (repost from prior bad
- CRLF on POST requests, where/how specified (repost from prior bad subject line)
- Downline U.S.A.!
- draft-ietf-tls-http-upgrade reissued
- E-mail name change for this user.
- FINANCIALLY FREE in LESS THAN 30 Minutes a Day
- FW: BCP 44, RFC 2964 on Use of HTTP State Management
- Fw: Last Call: On the use of HTTP as a Substrate for Other Protocols to
- Fw: Last Call: On the use of HTTP as a Substrate for Other Protocols to BCP
- FW: WG Action: HyperText Transfer Protocol (http) to conclude
- Has Netscape 5 become 6?
- Host header and URL
- How to turn your mailbox into a Money-Magnet
- HTTP
- HTTP Age Header Field (Section 14.6) - should overflow value be
- HTTP Age Header Field (Section 14.6) - should overflow value be 2^31
- HTTP Age Header Field (Section 14.6) - should overflow value be 2^31 or (2^31)-1?
- HTTP Age Header Field (Section 14.6) - should overflow value be 2^31 or (2^31)-1?
- HTTP entity length
- HTTP Format and How HTTP works
- HTTP image transfer
- Http overhead
- HTTP traffic statistics
- HTTP/1.1: RFC2068 versus RFC2616, RFC1590 versus RFC2048
- HTTP/proxy calls
- HTTP_REFERER
- HTTPs
- I've Developed The Perfect Hi-Tech, Hi-Touch, Home Business
- Idempotent sequences of methods
- IETF Adelaide and interim meetings for APPS WGs
- If-Modified-Since implementation question
- Improving HTTP/DAV status reporting
- IPv6 and HTTP (1.2?)
- Last Call for comments on "Delta encoding in HTTP"
- Last Call on delta encoding in HTTP/1.1
- Legal tokens
- local http-proxy with http in and https out
- Microsoft HTTP 1.1 Conformance?
- monitored????
- More On Persistent Connections...
- nit on IETF HTTP-WG charter page
- Non-transparent proxies and the Vary header field
- Of HTTP-over-SSL/TLS connection persistence
- Of HTTP/1.1 persistent connections and TCP Keepalive timer
- Of HTTP/1.1 persistent connections and TCP Keepalive timers
- On pipelining
- On pipelining -Reply
- On pipelining -Reply -Reply
- persistent conncetion HOL blocking
- problem with responses to post-requests
- protocol verification
- Proxies and incorrect Content-Length
- Proxies, Request-URI, and digest-uri
- Proxy-connection
- Push technology
- Question for HTTP/1.1 cache implementors (both proxy & client caches)
- Question of many METHODs
- Question on proxy/client behaviour
- Questions (errata?) about caching authenticated responses
- RE: "Via" header field
- RE: Browser support for request pipelining
- RE: Cache-Control
- RE: caching problems
- RE: Chunked sample message
- RE: Conformance Test for HTTP 1.1
- RE: CRLF on POST requests, where/how specified (repost from prior
- RE: CRLF on POST requests, where/how specified (repost from prior bad subject line)
- RE: draft-ietf-tls-http-upgrade reissued
- RE: Host header and URL
- RE: HTTP entity length
- RE: Http overhead
- RE: HTTP/1.1: RFC2068 versus RFC2616, RFC1590 versus RFC2048
- RE: IPv6 and HTTP (1.2?)
- RE: Legal tokens
- RE: Microsoft HTTP 1.1 Conformance?
- RE: monitored????
- RE: Of HTTP-over-SSL/TLS connection persistence
- RE: Of HTTP/1.1 persistent connections and TCP Keepalive timers
- RE: On pipelining
- RE: On pipelining -Reply
- RE: On pipelining -Reply -Reply
- RE: problem with responses to post-requests
- RE: Proxy-connection
- RE: Question of many METHODs
- RE: Question on proxy/client behaviour
- RE: Questions (errata?) about caching authenticated responses
- RE: Thanks Re Caching Problem
- RE: ticket based authentication
- RE: Use Proxy 305 (corrected)
- RE: user agent header question
- RE: Using Chunked encoding to send control messages to a client
- RE: webmail vulnerabilities: a new pragma token?
- Reference HTTP 1.1 Client And Server Implementations
- request to close HTTP-WG
- Requirements Summary
- Review of Platform for Privacy Preferences (P3P) requested
- Set-Cookie Header
- Spaces allowed between chunk size and semi-colon?
- subscribe
- test mail dont read this
- Testing web server speed
- Thanks Re Caching Problem
- The future of HTTP
- ticket based authentication
- TLS upgrade implementations?
- Two newish technical reports based on an HTTP trace
- Two questions
- Unidentified subject!
- Unlimited Free Long Distance!
- UNSUBSCRIBE
- Use Proxy 305 (corrected)
- Use Proxy 505
- user agent header question
- Using Chunked encoding to send control messages to a client
- WAP gateway and HTTP
- webmail vulnerabilities: a new pragma token?
- whither HTTP?
Last message date: Tue 08 Dec 1970 - 06:53:52 PST
Archived on: Wed Jan 31 2001 - 20:41:03 PST
This archive was generated by hypermail 1.02.