HTTP-WG Mailing List Archive for 1999 by subject
Starting: Sat 03 Jan 1970 - 11:30:59 PST
Ending: Wed 29 Dec 1999 - 15:09:50 PST
Messages: 360
- (no subject)
- 304 response with Content-Length header == OK?
- A proposal for Host header
- A proposed method for tracing broken links
- about TCP connection up timer in HTTP session
- Add On... #423B
- Apology for goof in posting SOAP V1 draft
- Asynchronous updates/notifications
- basic and md5 authentication
- Caching input - known problems
- Chunk size definition problem?
- Clarification on cacheability
- Clarification on cacheability
- Comments on HTTP TLS Upgrade draft
- CONNECT HELP
- Content-Range Problem !!
- Cookie doubt
- Correct behavior of reverse proxies WRT host field.
- Date header handling
- disposition of draft-ietf-http-* internet drafts
- Doubt regarding quoted-pair
- Download With Starting Byte !!
- draft-ietf-tls-http-upgrade-02 available
- Editorial note and question on connections
- errata for RFC 2616 & 2617
- Expires and 'non-cacheable'
- Failure to do persistent connection
- FINAL: minor editorial issues in draft-ietf-http-v11-spec-rev-06.txt
- Fragments in "Location" field
- Frames
- FW: generated hypertext (HTML) version of RFC2616 [yet again]
- General confusion about Cache-Control headers
- generated hypertext (HTML) version of RFC2616
- GET or method (HTTP 1.1 rev 6)
- GETs with Entity-Body ??
- GIF
- gif file
- Host header issue
- Http
- HTTP & SHTTP
- HTTP 1.1 rev 6 BNF erratum
- HTTP Errata Page
- Http Programming In Proxy !!
- http proxy & tunnel differences ??
- HTTP Server
- HTTP to "Standard"? When?
- http-wgrequest@hplb.hp.com
- HTTP/1.1 Error Responses
- HTTP/1.1 revision 6 concerns/issues
- https
- I-D ACTION:draft-hnrs-rmt-avt-feedback-00.txt
- I-D ACTION:draft-ietf-http-state-man-mec-11.txt,.ps
- I-D ACTION:draft-ietf-http-state-man-mec-12.txt,.ps
- IESG approves HTTP/1.1 as Draft Standard
- IPP> Chunked POST
- IPP> Chunked POST: SUMMARY
- IPP>MOD Should IPP notification use http as transport?
- Last Call: Applicability Statement for HTTP State Management to BCP
- Last Call: Upgrading to TLS Within HTTP/1.1 to Proposed Standard
- Last Call: Upgrading to TLS Within HTTP/1.1 to Proposed Standard
- MIME type setting
- Minneapolis
- minor editorial issues in draft-ietf-http-v11-spec-rev-06.txt
- mistaken reference to "unsafe" in RFC 2616
- more errata in RFC 2616
- Netscape-Enterprise http server - problem
- nice Fellow
- number lost (HTTP 1.1 rev 6 )
- Password change via HTTP
- Persistant Connection over proxy
- Please feedback: a proposed method for tracing broken links
- please remove me from this alias
- POST Headers
- pro-cow : protocol compliance on the web
- Problem
- Protocol Action: Hypertext Transfer Protocol -- HTTP/1.1 to
- Proxies and broken HTTP
- Proxies and persistent connections
- Proxy auth
- Proxy-Connection header definition?
- RE: A proposed method for tracing broken links
- RE: Asynchronous updates/notifications
- RE: Chunk size definition problem?
- RE: Clarification on cacheability
- RE: Comments on HTTP TLS Upgrade draft
- RE: Correct behavior of reverse proxies WRT host field.
- RE: Date header handling
- RE: disposition of draft-ietf-http-* internet drafts
- RE: errata for RFC 2616 & 2617
- RE: Expires and 'non-cacheable'
- RE: Fragments in "Location" field
- RE: Frames
- RE: Host header issue
- RE: http proxy & tunnel differences ??
- RE: https
- RE: IPP> Chunked POST
- RE: IPP> Chunking Explanation
- RE: IPP>MOD Should IPP notification use http as transport?
- RE: Last Call: Applicability Statement for HTTP State Management
- RE: Last Call: Applicability Statement for HTTP State Management to BCP
- RE: Last Call: Applicability Statement for HTTP State Management to BCP
- RE: Last Call: Upgrading to TLS Within HTTP/1.1 to Proposed Standard
- RE: MIME type setting
- RE: Minneapolis
- RE: minor editorial issues in draft-ietf-http-v11-spec-rev-06.txt
- RE: mistaken reference to "unsafe" in RFC 2616
- RE: Password change via HTTP
- RE: Persistant Connection over proxy
- RE: Protocol Action: Hypertext Transfer Protocol -- HTTP/1.1 to Draft Standard
- RE: Proxies and broken HTTP
- RE: Proxy-Connection header definition?
- RE: rfc2617: BNF for 'domain'
- RE: rfc2617: response-auth calculation
- RE: server parsing of URI path parameters
- RE: SOAP
- RE: terminology question
- RE: Upgrading to TLS Within HTTP/1.1 draft available
- RE: want to set my pages to expire but can't find info on date format expected ...
- RE: WG meeting in Washington?
- RE: What's the mechanism for adding new error codes?
- Redirection messages for proxy clients
- Refresh: header specs.
- Remaining editorial issues
- Remaining editorial issues)
- RequestStartSec and RequestStartUsec
- rfc2617: BNF for 'domain'
- rfc2617: response-auth calculation
- Semantics of chunk-exts?
- Server Didn't Send Content-Length !!
- server parsing of URI path parameters
- Server Which Didn't Send Content-Length !!
- Server-side roles in the HTTP
- simple http-proxy ?
- Slides available from my USENIX talk
- some questions and notes on HTTP/1.1 rev 6
- Standardize Kerberos authentication and authorization in HTTP?
- terminology question
- Test mail
- Thanks ( Content Range ) !!
- The HTTP 'link' and 'Content-Base' Headers
- To Know Filesize Without Content-Length !!
- Tokens for requesting/indicating upgrade
- typo in draft-ietf-http-v11-spec-rev-06
- Unidentified subject!
- Unidentified subject!)
- Upgrading to TLS Within HTTP/1.1 draft available
- want to set my pages to expire but can't find info on date format
- want to set my pages to expire but can't find info on date format expected ...
- WG meeting in Washington?
- What's the mechanism for adding new error codes?
- working of http request and response!!
- Working with COOKIES ....
- World's smallest Web server....
Last message date: Wed 29 Dec 1999 - 15:09:50 PST
Archived on: Tue Jan 04 2000 - 10:53:38 PST
This archive was generated by hypermail 1.02.