HTTP-WG Mailing List Archive for Q2, 1997 by subject
Starting: Tue 01 Apr 1997 - 02:18:10 PDT
Ending: Mon 30 Jun 1997 - 12:13:04 PDT
Messages: 644
- "last call": draft-ietf-http-versions-01.txt
- "versions" -> Informational RFC
- 1xx Clarification
- 1xx Clarification)
- 305/306 response codes
- A linguistic note on unverifiable transactions
- A new suggestion on 100 CONTINUE
- Accept header and inline images
- Administrivia: running on automatic
- An experiment in producing RFC1122-style requirements checklist
- Announcement: A new Wiley book on World Wide Web Security
- announcing: http-state mailing list
- Assigned paths
- Back from the grave: Unverifiable Transactions and Cookies
- Buggy TCP implementations. Was: ISSUE: MUST a client wait for 100 when doing PUT or POST requests?
- cache-busting and charsets again
- cache-busting document
- 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?
- Change to Chunk Length Syntax
- charsets again
- Comment on PEP draft
- COMMENT: LAST CALL comment
- COMMENT: resolution
- Comments on PEP draft
- Common Gateway Interface
- confidentiality and the referer field
- Cookie domain
- Date/time on the Internet
- DES attack, help crack bad encryption!
- Digest Authentication bleat
- Digest Authentication, Netscape, and Microsoft
- Document Action: Use and interpretation of HTTP version numbers to
- draft minutes, HTTP-WG meetings April
- draft minutes, HTTP-WG meetings April 7
- draft minutes, HTTP-WG meetings April 7)
- draft-daviel-metadata-link-00.txt
- draft-ietf-http-negotiate-scenario.00.txt
- draft-ietf-http-negotiation-02.txt
- draft-ietf-http-state-man-mec-01 submitted
- draft-mutz-http-attributes-02.txt
- Feature negotiation requirements
- feature negotiation syntax
- First draft of negotiation requirements document
- FREE LISTING in Worldwide Directory
- from the AD: content-length is invalid within multipart
- ftp URL stuff (was MIME multipart/* vs HTTP)
- FTP urls
- FW: Proposed amendment to RFC2109
- Graham Klyne on content negotiation
- HTTP 1.1 Issue: 403VS404
- HTTP 1.1 Issue: When To Close Connections
- HTTP Connection Management(draft-ietf-http-connection-00.txt)
- HTTP Connection Management(draft-ietf-http-connection-00.txt))
- HTTP Download
- HTTP Issues LAST CALL; HTTP editing group
- HTTP practice and Year-2000: the bad(?) news
- HTTP State Management Mechanism (Rev1): EndSession attribute
- HTTP/1.1 - Retry-after for 3xx as well as 503?
- HTTP/1.1 -- who disconnects the session?
- HTTP/1.1 Pipelining
- I-D ACTION:draft-cohen-http-305-306-responses-00.txt
- I-D ACTION:draft-ietf-http-jaye-trust-state-00.txt
- I-D ACTION:draft-ietf-http-negotiate-scenario-00.txt
- I-D ACTION:draft-ietf-http-negotiation-02.txt
- I-D ACTION:draft-ietf-http-pep-03.txt
- I-D ACTION:draft-ietf-http-state-man-mec-01.txt, .ps
- I-D ACTION:draft-ietf-http-state-man-mec-02.txt, .ps
- ID: Proxy autoconfig
- Ignore proxy
- Indexing non-HTML objects
- Insisting on a message digest (rfc2069)
- IPP> MIME multipart/* vs HTTP
- IPP>PRO - http comments
- Is Your Web Site A Secret?
- Issue: 304-LAST-MODIFIED (Should 304 include Last Modified?)
- Issue: BYTE-RANGE (Is the right meta-data returned on range
- Issue: BYTE-RANGE -- resolved?
- 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?
- Issues-list item "CACHING-CGI"
- Issues-list item "DISPOSITION"
- Issues-list item "LWS-DELIMITER"
- Issues-list item "QZERO"
- Memphis followup
- Memphis followup)
- mid-course errors
- MIME multipart/* vs HTTP
- More thoughts on content negotiation
- MUST a client wait for 100 when doing PUT or POST?
- New content negotiation draft: draft-ietf-http-negotiation-02.txt
- new cookie I-D submitted
- New feature negotiation syntax
- New PEP draft available as ID!
- New Proposed Chunked Rules
- no one supports Digest
- notes from previous Editing Group meeting: goals, docking
- NUDGE: Our piece on Host: and URLs (Fwd)
- OPS specification
- OPTIONS method
- Origin Servers without Clocks
- PEP Integration in RTSP
- Persistent connections, and 1.0 browsers
- Pipelining and compression effect on HTTP/1.1 proxies
- privacy platforms
- problems with cookies
- Process for closing out issues list
- Proposal: 100-Continue optional under Client control
- Proposal: Vary on Cookies
- Proposed amendment to RFC2109
- proxy autoconfiguration
- Proxy Keep-Alive
- Q: protocolls and fault tolerance
- Question
- RANGE-ERROR issue: proposed resolution
- RANGES (Might be nice to allow 206 response to range request
- RE: 1xx Clarification
- RE: 305/306 response codes
- RE: An experiment in producing RFC1122-style requirements checkli
- RE: confidentiality and the referer field
- RE: Digest Authentication bleat
- RE: Digest Authentication, Netscape, and Microsoft
- RE: e-mail
- RE: HTTP State Management Mechanism (Rev1): EndSession attribute
- RE: ID: Proxy autoconfig
- RE: Indexing non-HTML objects
- 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-list item "CACHING-CGI"
- RE: mid-course errors
- RE: MIME multipart/* vs HTTP
- RE: MUST a client wait for 100 when doing PUT or POST?
- RE: New feature negotiation syntax
- RE: New PEP draft available as ID!
- RE: PEP Integration in RTSP
- RE: Pipelining and compression effect on HTTP/1.1 proxies
- references to obsolete RFC1522
- Request for HTML Draft to support Multi Direction languages.
- request for input of managing WWW-servers.
- Revised charter ,
- Revised charter , milestones
- Revised charter ,milestones
- Revised charter milestones
- Rewrite of feature tag syntax rules
- Slight wording error in section 13.5.4
- SSL tunneling status
- State management
- Status 100
- Summary, HTTP-WG meeting in Memphis
- Transient content negotiation
- Unidentified subject!
- Updated Issues list...
- Updated test implementation for TCN available
- URI -> URL when talking about 'moved ...'
- Web Security
- Web Site Visibility
- WEB->FAX
- webmaster@website
Last message date: Mon 30 Jun 1997 - 12:13:04 PDT
Archived on: Thu Jul 03 1997 - 17:30:36 PDT
This archive was generated by hypermail 1.02.