HTTP-WG Mailing List Archive for Q3, 1995 by subject
Starting: Mon 03 Jul 1995 - 03:35:54 PST
Ending: Sat 30 Sep 1995 - 21:59:07 PST
Messages: 816
- "Hits" pragma
- '205 Reset Document' (was Any more comments?)
- (no subject)
- (Secure) HTTP library API ?
- 406 None Acceptable
- 411 response code: clarification, please
- A modest proposal
- A modest proposal)
- A modest proposal, made more specific
- Accept headers and media parameters
- Agenda Items for working group meeting
- an idempotent idea (think it twice - see what happens)
- any more comments?
- any more comments? ('204 No Content' clarification)
- Beth Frank: Question about Host
- Browser Interpretation of Location: Header
- Cache-control: max-age, uh, where?
- Cacheable extension methods (was: an idempotent idea)
- caching related topics in the draft and the http-wg discussion
- Color content negotiation
- Color content negotiation)
- Comment on http 1.0 draft 01: authentication and caching
- Comments on draft-v10-03a.
- Comments on ETRN draft
- Comments on HTTP/1.0 Draft 3
- Complaints regarding Draft Status and Author
- Content Codings
- Content-Transfer-Encoding
- Content-Transfer-Encoding "packet"
- Cookies
- De Re If-Modified-Since
- Defn of Location in 200, 301, and 302
- difference between URI and URL (was: Question)
- domain name)
- domain-name?
- domain-name? (fwd)
- Draft Minutes of HTTP Working Group, 33rd IETF Meeting,
- Draft Minutes of HTTP Working Group, 33rd IETF Meeting, Stockholm
- draft-eastlake-internet-payment-00.txt
- draft-luotonen-http-url-byterange-00.txt
- Event-driven document expiration
- 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
- Globalizing URIs
- Glossar: reload, refresh, no-cache
- HEAD and 301/302/303 conflict?
- HEAD request & HTTP-EQUIV meta tag
- help
- Host: vs. Orig-URI: w/ %%
- HTTP & WAIS
- HTTP protocol requirements (was: Draft Minutes of HTTP Working Group, 33rd IETF Meeting, Stockholm)
- HTTP Session Extension draft
- http spec
- HTTP version 1.0 or 1.1?
- 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 Internet-Draft 01 Available
- HTTP/1.0 Review Plan
- HTTP/1.2 stuff: try it out!
- HTTP/1.2 stuff: try it out!
- I-D ACTION: draft-luotonen-http-url-byterange-00.txt
- I-D ACTION:draft-ietf-http-ses-ext-00.txt
- I-D ACTION:draft-ietf-http-v10-spec-01.txt, .ps
- I-D ACTION:draft-ietf-http-v10-spec-02.txt, .ps
- I-D ACTION:draft-ietf-http-v10-spec-03.txt, .ps
- I-D ACTION:draft-kristol-http-state-info-00.txt, .ps
- I-D ACTION:draft-kristol-http-state-info-01.txt, .ps
- Idempotent
- If-Modified-Since and forged dated
- Improving If-Modified-Since
- Is HTTP a better replacement for FTP ?
- Keep Alives/Session Extension
- Keep-Alive: "Max" or "Maxreq"?
- keepalive/lookahead
- list of pending proposals
- location of draft-v10-03a
- Location Proposals
- Location Proposals)
- Location, URI-header, etc.
- Looking for draft version of http 1.1
- more http-v10-spec-01
- more If-Modified-Since
- multiple Content-Encoding
- Negotiation in draft 01
- new State-Info draft available
- Non-persistent Cookie proposal
- Persistent connections and error conditions
- Persistent connections: aborting requests in progress.
- planned obsolescence
- Possible optimization to State-Info proposal
- posts to both www-talk and http-wg
- potential security holes in digest authorization
- Preemptive and
- Preemptive and reactive content negotiation
- Preemptive and reactive content negotiation)
- Proposal: Checksum header or method
- Proposal: a PLAY or STREAM method for http/1.1
- Proposal: Checksum header or method
- PUT
- Q: A Solution for Multi-Identity Multi-Home HTTP Servers ?
- Question
- Question about the HTTP service.
- questions -- clarifications requested
- questions, clarifications on 301 and 302 responses
- RE: any more comments?
- RE: HTTP version 1.0 or 1.1?
- RE: idempotent
- RE: Persistent connections: aborting requests in progress.
- RE: questions -- clarifications requested
- RE: Suggestion: Partial file transfer.
- RE: UDP or TCP?
- Reaad my Pages!
- reality check: HTTP comments
- realms, prompts, WWW-Authenticate
- reload discussion
- Report: Problems with the Expires header.
- request-method POST
- Server capabilities investigation
- Session-ID -> State-Info
- Session-ID proposal
- Session-ID proposal update
- snapshot
- specification language
- State-Info is too fragile...
- Status and Consensus on Host
- Still trying to make sense of HTTP caching model
- Stockholm IETF
- Suggestion: Partial file transfer.
- Suggestion: PUT if-not-modified-since
- The Case for Persistent-Connection HTTP, by Jeff Mogul.
- The IETF process
- The Standards Process
- Transfer-Encoding: questions not answered
- Transfer-Encoding: questions not answered
- two more pending proposals
- UDP or TCP
- UDP or TCP?
- updated State-Info proposal
- WG last call on HTTP/1.0
- WG last call on HTTP/1.0 - Request for URL clarification
- WG last call on HTTP/1.0 -- Where's Accept:?
- What happened to Retry-After and 503?
- Where send comments to?
- WWW I18N at Unicode Conference (Sept 14/15)
- WWW Servers Comparison Chart, version 2.3
- WWW Servers Comparison Chart, version 2.4
Last message date: Sat 30 Sep 1995 - 21:59:07 PST
Archived on: Sun Oct 29 1995 - 21:06:36 PST
This archive was generated by hypermail 1.02.