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!
- HTTP/1.2 stuff: try it out!
- HTTP: T-T-T-Talking about MIME Generation
- HTTP: multiple-get (was: T-T-T-Talking about MIME Generation)
- HTTP: T-T-T-Talking about MIME Generation
- http://info.cern.ch/hypertext/WWW/Protocols/Overview.html
- I-D ACTION: draft-luotonen-http-url-byterange-00.txt
- I-D ACTION:draft-ietf-http-digest-aa-00.txt
- I-D ACTION:draft-ietf-http-digest-aa-01.txt
- I-D ACTION:draft-ietf-http-digest-aa-02.txt
- I-D ACTION:draft-ietf-http-mda-00.txt
- I-D ACTION:draft-ietf-http-ses-ext-00.txt
- I-D ACTION:draft-ietf-http-v10-spec-00.txt, .ps
- 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-ietf-http-v10-spec-04.txt, .ps
- I-D ACTION:draft-ietf-http-v11-spec-00.txt, .ps
- I-D ACTION:draft-kristol-http-state-info-00.txt, .ps
- I-D ACTION:draft-kristol-http-state-info-01.txt, .ps
- I-D ACTION:draft-luotonen-ssl-tunneling-01.txt
- i18n and the WWW
- Idempotent
- If-Modified-Since and forged dated
- Improving If-Modified-Since
- Indexing extension
- Indexing extension (fwd)
- interaction of caching with content negotiation, authentication, state, etc
- Is HTTP a better replacement for FTP ?
- ISO/IEC 10646 as Document Character Set
- ISPP BOF report
- keep alive
- keep alive (fwd)
- Keep Alives/Session Extension
- Keep-Alive Notes
- Keep-Alive: "Max" or "Maxreq"?
- keepalive/lookahead
- keepalives again
- Keepalives and proxies (hopefully solved)
- keepalives and proxies: a request and a proposal
- Language Tags
- List of HTTP servers
- list of pending proposals
- list of URIs in authorization realm
- location of draft-v10-03a
- Location Proposals
- Location Proposals)
- Location, URI-header, etc.
- logic bag
- Logic Bag concerns
- Logic Bag concerns (with some proposals)
- Logic Bag concerns)
- logic bag syntax
- Looking for draft version of http 1.1
- Lynx Client Code (UNIX/C only)
- making progress on State-Info
- March 8 Internet Draft of HTTP/1.0
- Methods missing
- Middleware Workshop(ACM SIGCOMM)
- MIME and binary transport
- Minutes from Danvers?
- Minutes of Hypertext Transfer protocol BOF at 31st IETF
- minutes, HTTP Working Group
- Mirroring
- More content negotiation
- More followups
- more http-v10-spec-01
- more If-Modified-Since
- More notes on content negotiation
- Moving HTTP 1.0 to informational
- Multilingual WWW
- multipart in HTTP/1.0 draft
- multiple Content-Encoding
- NCSA implementation of KeepAlive
- NCSA implementation of KeepAlive (fwd)
- NCSA implementation of KeepAlive [Mac TCP issues]
- NCSA implementation of KeepAlive [server overload issues]
- Negotiation in draft 01
- New byteranges
- New draft; Content-Length
- New IETF Draft 00 of HTTP/1.0
- New mailing list for http-ng
- New response code
- New specification document for S-HTTP version 1.1
- New Standards
- new State-Info draft available
- new version of extensions proposal
- New Web server for OS/2
- no "conforming" HTTP/1.0
- No More Passwords In The Clear in HTTP!
- Non-persistent Cookie proposal
- On the connection between content negotiation and caching
- On the problem of TCP-connection hijacking
- One paragraph summary of the HTTP-BOF
- Opaque
- open/request/close in one packet?
- Original 'accept-hash' post:
- original host name in request/header
- partial URLs ?
- partial URLs ? (was
- partial URLs ? (was <p> ... </p>)
- Paul Leach: RE: Formation of persistent connections subgroup
- Persistent connections and error conditions
- Persistent connections: aborting requests in progress.
- Philip Thrift: chunked transfer of video data in Keep-Alive connections
- planned obsolescence
- Possible New Optional Field in Heade
- Possible New Optional Field in Header?
- Possible optimization to State-Info proposal
- posts to both www-talk and http-wg
- Potential HTTP Security Risk
- potential security holes in digest authorization
- Preemptive and
- Preemptive and reactive content negotiation
- Preemptive and reactive content negotiation)
- proposal for a new html tag
- Proposal for HTTP Extension Mechanism
- Proposal for new authentication scheme
- Proposal: Checksum header or method
- Proposal: a PLAY or STREAM method for http/1.1
- Proposal: Checksum header or method
- Proposed new authentication scheme for HTTP
- Propsal: MHEAD for Fast inline image formatting Was: Multiple connections
- Protecting heirarchies
- Proxies and loops
- Proxy naming
- PUT
- Q on HTTP/1.0 Sec. 11.2 Idempotent Methods
- Q: A Solution for Multi-Identity Multi-Home HTTP Servers ?
- Q: HTTP/1.0 being "...stateless, object-
- Quality factors (http draft 8th March)
- Query on 5.5.8 Accept
- Question
- Question about "406 None Acceptable"
- Question about POST in HTTP/1.0
- Question about the HTTP service.
- questions -- clarifications requested
- questions on http-draft oct14 1995
- questions, clarifications on 301 and 302 responses
- RE: A few semantic points for HTTP/1.0 draft
- RE: any more comments?
- RE: Decision about Host?
- RE: DNS vs HOME PAGE[S]?
- RE: Experimental implementation of SimpleMD5
- RE: HTTP version 1.0 or 1.1?
- RE: idempotent
- RE: Moving HTTP 1.0 to informational
- RE: Persistent connections: aborting requests in progress.
- RE: Proxy naming
- RE: questions -- clarifications requested
- RE: Revised Charter
- RE: safe PUT
- RE: Suggestion: Partial file transfer.
- RE: Two proposals for HTTP/2.0
- RE: UDP or TCP?
- RE: User authentication for the proxy
- Reaad my Pages!
- Reading Request Object Data
- reality check: HTTP comments
- Really-From: allowing for proxying problems.
- realms, prompts, WWW-Authenticate
- Redirection inherits METHOD?
- Reference to 2nd WWW Conference paper on HTTP latency
- Referer (sic)
- Referer: (sic)
- Release of WRL "persistent-connection" HTTP implementation
- reload discussion
- Reopening RFC 1766 - Language Tags
- Report: Problems with the Expires header.
- Request for help
- request identifiers in HTTP
- request-method POST
- rethinking caching
- Rethinking content negotiation (Was: rethinking caching)
- review of byte range draft: please reply
- Revised agenda for IETF BOF on 7th December 1994
- Revised Charter
- Revised Charter)
- revised charter?
- Round 2: moving HTTP 1.0 to informational
- safe PUT
- Semantics of "Accept:"
- Server capabilities investigation
- Server Hacking
- Server Hacking)
- session id vs. cookies
- Session-ID -> State-Info
- Session-ID proposal
- Session-ID proposal update
- Shen Digest Authentication scheme available.
- Sign-Off
- SimpleMD5 access authentication, second draft
- SimpleMD5 quibbles
- snapshot
- Solaris HTTP server performance...
- Solaris HTTP server performance... (fwd)
- Some notes on content negotiation
- Some questions on the draft HTTP document
- Son of MIME (was comments)
- specification language
- State Wars, part XI (was: Revised Charter)
- State-Info is too fragile...
- Statistics on reusing request headers in persistent connections
- Statistics on reusing request)
- Status and Consensus on Host
- Status of negotiation text in 1.1 draft?
- Status of PUT?
- still more Digest Authentication comments
- Still trying to make sense of HTTP caching model
- Stockholm IETF
- subscribe
- subscribe html-wg howcome@dxcern.cern.ch
- Subscription request
- Subscription to Mailing List
- subsrcibe
- Suggestion for HTTP 1.0
- Suggestion: HTTP Timezone header
- 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
- Time for HTTP WG BOF
- TIME_WAIT
- Transfer-Encoding: questions not answered
- Transfer-Encoding: questions not answered
- two more pending proposals
- Two proposals for HTTP/2.0
- two-phase send concerns )
- two-phase send concerns
- two-phase send concerns )
- UDP or TCP
- UDP or TCP?
- unsubscribe
- updated State-Info proposal
- URI fields in response headers
- User authentication for the proxy
- using opaque strings to determine uniqueness
- v10-spec-00 comments
- Vulnerabilities in digest-aa I-D
- Welcome to winter
- WG Action: HyperText Transfer Protocol (http)
- 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 can you cache? [was: Byte ranges -- formal spec proposal ]
- What happened to Retry-After and 503?
- What the heck am I doing?
- What to do on byte ranges?
- Where is the latest draft
- Where send comments to?
- Where should Digest go next?
- Where to estimate "link speed", and
- Where to estimate "link speed", and why not
- Which Doc is for which HTTP version?
- Which usual media types can a server send
- Whither Digest AA
- Whither mxs? [was: Possible New Optional Field in Header?]
- Why is From: limited?
- Why is Message-ID header in HTTP?
- WIDTH and HEIGHT
- WInter (Web Internationalization & Multilinguism)
- WIT, Was: Comments please on agenda for HTTP working group BOF
- Worries about content-length
- WWW I18N at Unicode Conference (Sept 14/15)
- WWW Servers Comparison Chart, version 2.1
- WWW Servers Comparison Chart, version 2.2
- WWW Servers Comparison Chart, version 2.3
- WWW Servers Comparison Chart, version 2.4
Last message date: Tue 09 Jan 1996 - 04:20:54 GMT
Archived on: Tue Jan 09 1996 - 04:23:46 GMT
This archive was generated by hypermail 1.02.