HTTP-wg Archive by subject
Starting: Fri 30 Sep 1994 - 16:05:16 GMT
Ending: Tue 09 Jan 1996 - 04:20:54 GMT
Messages: 2287
- "Expires" again...
- "Hits" pragma
- '205 Reset Document' (was Any more comments?)
- 'Full-URI' considered vague
- 'Full-URI' header
- 'PUT' transaction reconsidered)
- (hopefully) last message on WG process
- (hopefully) last question
- (no subject)
- (none)
- (Secure) HTTP library API ?
- 3.3.1 Full date
- 3rd party Digest Access Authentication
- 401 Unauthorized - can I use it?
- 406 None Acceptable
- 411 response code: clarification, please
- 502 or 503
- 502 result code
- [more about IMG attributes for size]
- [www-mling,00149] Accept-Charset
- [www-mling,00154] charset parameter (long)
- A few semantic points for HTTP/1.0 draft
- A modest proposal
- A modest proposal)
- A modest proposal, made more specific
- A Proposed Extension to HTTP : SimpleMD5 Access Authentication
- A truly multilingual WWW
- Accept headers and media parameters
- Actual treatment of End-of-Line in different browsers
- additional response status codes
- Administrivia: bounced messages
- Administrivia: http-wg mailing list UP!
- Administrivia: List unsupervised for 2 weeks
- Agenda for Dallas IETF meeting
- Agenda for HTTP-WG meeting at Dallas
- Agenda Items for working group meeting
- an idempotent idea (think it twice - see what happens)
- ANNC: Draft of "PEP: An Extension Mechanism for HTTP" avail.
- another Digest Access Authentication
- another Digest Access Authentication question
- another Digest Access Authentication question
- another Digest test
- Anselm Baird_smith: Authentication spaces
- any more comments?
- any more comments? ('204 No Content' clarification)
- Authentication spaces
- Authorship?
- Beth Frank: Question about Host
- Browser Developers (A Plea From BrowserWatch)
- Browser Interpretation of Location: Header
- Byte ranges -- formal spec proposal
- Byteranges with 206 partial content
- Cache-control: max-age, uh, where?
- Cacheable extension methods (was: an idempotent idea)
- Caching data returned from POST, and conditional POST
- caching related topics in the draft and the http-wg discussion
- CGI???
- CHaracter representation negotiation
- character sets in HTTP: translation tables
- charset overlabeling
- charset parameter (long)
- charset Reality Check
- charset= history, proposal
- Clarification on language tag usage in latest draft
- Clarification on language tag usage in latest draft: take 2
- Closure on canonicalization, I hope
- Color content negotiation
- Color content negotiation)
- Comment on http 1.0 draft 01: authentication and caching
- comments in HTTP headers
- Comments on Byte range draft
- Comments on draft-ietf-http-v10-spec-00.ps
- Comments on draft-ietf-http-v10-spec-00.txt
- Comments on draft-v10-03a.
- Comments on ETRN draft
- Comments on HTTP draft [of 23 Nov 1994]
- Comments on HTTP/1.0 Draft 3
- Comments on HTTP/1.0 draft [March 8, 1995]
- Comments on latest draft
- comments on Robinson's CGI spec.
- Comments on the HTTP/1.0 draft.
- Comments please on agenda for HTTP working group BOF
- Comments please on agenda for HTTP working group BOF)
- Complaints regarding Draft Status and Author
- Connection Header
- Connection Oriented HTTP conflict
- Content Codings
- Content negotiation and MIME registration procedures
- Content-Digest draft, request for ...
- Content-Digest header
- content-language
- content-length vs. boundary markers
- Content-MD5
- Content-Transfer-Encoding
- Content-Transfer-Encoding "packet"
- Cookies
- CRLF
- Dallas IETF meeting of HTTP-WG
- Daniel DuBois: More content negotiation
- De Re If-Modified-Since
- Decision about Host?
- Defn of Location in 200, 301, and 302
- Deployment of Format negociation (sic)
- Deployment of Format negociation [was: Suppressed content in HEAD: myth or reality?]
- difference between URI and URL (was: Question)
- Digest Access Authentication
- Digest Access Authentication proposal - "Authorization"
- Digest Auth...
- Digest Authentication
- Digest Authentication. Moving towards last call...
- Dilbert, the Next Generation
- Disagree: Multiple connections
- Distribute copy of a document?
- DNS vs HOME PAGE[S]?
- Document SimpleMD5 weakness to man-in-the-middle attack
- domain name)
- domain-name?
- domain-name? (fwd)
- Draft 01 of HTTP/1.0
- Draft Minutes of HTTP Working Group, 33rd IETF Meeting,
- Draft Minutes of HTTP Working Group, 33rd IETF Meeting, Stockholm
- DRAFT Minutes, HTTP-WG
- DRAFT Minutes, HTTP-WG)
- draft-eastlake-internet-payment-00.txt
- draft-kristol-http-extensions-00.{ps,txt}
- draft-luotonen-http-url-byterange-00.txt
- Effects of Persistent Connections
- Event-driven document expiration
- Experimental implementation of SimpleMD5
- Expires head count
- Expires, Last-Modified, Pragma: no-cache etc.
- Expires, Last-Modified, Pragma: no-cache, and PRIVACY
- fast rendering of text, containing images (Was: Persistent ...)
- forged dates and other anti-cache practices
- Formalizing Expires, Last-Modified, "data object"
- Formation of caching subgroup
- Formation of persistent connections subgroup
- FTP-able archive of HTTP-WG mail?
- Full-URI, again
- Further revision of the agenda for IETF BOF on 7th December 1994
- FWD>Adobe Acrobat 2.1 announced
- FYI: Summary #1 of byte ranges
- gag me with a spoon
- Getting full URI to the server
- Globalizing URIs
- Glossar: reload, refresh, no-cache
- Grammar for User-Agent header
- Grievances - Focused
- Grievances - Wide
- Harrie Hazewinkel: announcement http-mib mailing list
- Harvest cache now available as an ``httpd accelerator''
- HEAD and 301/302/303 conflict?
- HEAD request & HTTP-EQUIV meta tag
- Header fields missing
- help
- Help me for HTML editors
- Henrik Frystyk Nielsen: Hypertext Version ready of HTTP Spec
- host fqdn
- Host header
- Host header (and Proxies)
- Host: fqdn
- Host: vs. Orig-URI: w/ %%
- How are/should redirects of POSTS be handled
- HTTP & WAIS
- http - htmp - spec
- HTTP - why not multiple connections?
- HTTP 1.1 Unless header
- HTTP 1.1 wish list page?
- HTTP and Media Serving
- HTTP BOF at WWW4: Wednesday 7pm
- HTTP Caching Model?
- HTTP Caching Model?)
- HTTP extension
- HTTP POST streaming
- HTTP protocol requirements (was: Draft Minutes of HTTP Working Group, 33rd IETF Meeting, Stockholm)
- HTTP security risks
- HTTP Session Extension draft
- HTTP should be able to transfer part of a document
- http spec
- HTTP status code for "Password Expired"?
- HTTP version 1.0 or 1.1?
- HTTP WG meeting in Dallas: Summary
- HTTP-1.1 and HTTP-NG?
- HTTP-NG checkpoint 2
- http-ng mailing list now better
- http-v10-spec-01.ps nits
- HTTP/1.0 draft 01 (quick note)
- HTTP/1.0 draft 02
- HTTP/1.0 Draft 3 defines both 0.9 and 1.0 ?
- HTTP/1.0 draft status
- HTTP/1.0 draft status)
- HTTP/1.0 Internet-Draft 01 Available
- HTTP/1.0 Issues
- HTTP/1.0 Review Plan
- HTTP/1.0 Specification and HTTP-WG Archives
- HTTP/1.1 draft 00 : chunked transfer and proxies
- HTTP/1.1 draft 00 is available
- HTTP/1.1 issues
- HTTP/1.2 stuff: try it out!