ietf-http-wg@w3.org from October to December 2010 by subject

"refresh" header

#229: Considerations for registering new status codes

#230: Considerations for registering new methods

#233: Is * usable as a request-uri for new methods?

#243: iso-8859-1 in C-D

#250 / #251 (connect bodies)

#251 (connect bodies), was: Proposal: 205 Bodies [#88]

%encoding in filename parameters. Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02

1st CFP: IJCAI-11 Workshop on Discovering Meaning On the Go in Large & Heterogeneous Data (LHD-11)

[#177] Realm required on challenges

[#193] Trailers and intermediaries

[#203] Max-forwards and extension methods

[#259] Handling invalid Content-Dispostion headers

[#95] Multiple Content-Lengths

[apps-discuss] [kitten] [saag] HTTP authentication: the next generation

[apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation

[apps-discuss] HTTP authentication: the next generation

[AVT] Fw: [httpstreaming] Agenda and Slides

[http-auth] [saag] [websec] [kitten] HTTP authentication: the next generation

[http-auth] [websec] [kitten] [saag] HTTP authentication: the next generation

[http-auth] [websec] HTTP authentication: the next generation

[httpstreaming] Agenda and Slides

[httpstreaming] Time and location for HTTP streaming bar BoF

[hybi] workability (or otherwise) of HTTP upgrade

[kitten] [apps-discuss] [saag] HTTP authentication: the next generation

[kitten] [saag] HTTP authentication: the next generation

[saag] [apps-discuss] [websec] [kitten] HTTP authentication: the next generation

[saag] [http-auth] [websec] [kitten] HTTP authentication: the next generation

[saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation

[saag] [websec] [kitten] [apps-discuss] HTTP authentication: the next generation

[saag] HTTP authentication: the next generation

[websec] [apps-discuss] [kitten] [saag] HTTP authentication: the next generation

[websec] [saag] [apps-discuss] [kitten] HTTP authentication: the next generation

[websec] [saag] HTTP authentication: the next generation

[websec] HTTP authentication: the next generation

API Rate Limits and HTTP Code

API Rate Limits and HTTP Code [#255]

Call for feedback: HTML application cache

chunk-extensions

Comments on draft-ietf-httpbis-content-disp

Comments on Section 6.1

CONNECT command with message body

Content Auto-negotiation

Content-Disposition

Content-Disposition next steps

Content-Location on 200 responses

Date format glitch

detecting support for percent encoding in C-D, was: repeated filename parameters

Does no-store in request imply no-cache?

Does no-store in request imply no-cache? [#249]

draft-bryan-metalinkhttp-18.txt

draft-yevstifeyev-http-headers-not-recognized-01.txt

Extending redirects to suggest updated locations ?

First part of LC for draft-yevstifeyev-http-headers-not-recognized summary

Fwd: [apps-discuss] Fwd: WG Review: Web Security (websec)

Fwd: [websec] request for feedback on adoption of drafts to WG - until Dec-16

Fwd: Content-Disposition and IE

Fwd: Does no-store in request imply no-cache?

Fwd: I-D Action:draft-zong-httpstreaming-gap-analysis-01.txt

Fwd: Last Call: <draft-ietf-httpstate-cookie-18.txt> (HTTP State Management Mechanism) to Proposed Standard

Fwd: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC

Fwd: RFC 5988 on Web Linking

fyi: draft-ietf-httpstate-cookie-15.txt

Headers-Not-Recognized for HTTP

Headers-Not-Recognized for HTTP (was: Please review my Internet-Draft)

HTTP authentication: the next generation

httpbis -12 drafts

I-D Action:draft-ietf-httpbis-authscheme-registrations-00.txt

I-D Action:draft-ietf-httpbis-content-disp-03.txt

I-D Action:draft-ietf-httpbis-content-disp-04.txt

I-D Action:draft-ietf-httpbis-p1-messaging-12.txt

I-D Action:draft-ietf-httpbis-p2-semantics-12.txt

I-D Action:draft-ietf-httpbis-p3-payload-12.txt

I-D Action:draft-ietf-httpbis-p4-conditional-12.txt

I-D Action:draft-ietf-httpbis-p5-range-12.txt

I-D Action:draft-ietf-httpbis-p6-cache-12.txt

I-D Action:draft-ietf-httpbis-p7-auth-12.txt

I-D Action:draft-nottingham-http-portal-01.txt

I-D Action:draft-zong-httpstreaming-gap-analysis-01.txt

Identifying the Resource Associated with a Representation?

Issue 141: "should we have an auth scheme registry"

Issue 160 (Redirects and non-GET methods)

issue 226, "proxies not supporting certain methods"

Issue 240: Migrate Upgrade details from RFC2817

Issue 244 (repeated parameters), was: Working Group Last Call: Content-Disposition

Issue 245 (percent escaping), was: Working Group Last Call: Content-Disposition

Issue 248: client "Date" requirements

issue 258, was: Comments on draft-ietf-httpbis-content-disp

Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp

Issue 263 (text about historical percent-decoding unclear), was: Comments on draft-ietf-httpbis-content-disp

issue 264: language tagging, was: Comments on draft-ietf-httpbis-content-disp

Issue 265: Clarify that C-D spec does not apply to multipart upload

language tag support, was: Comments on draft-ietf-httpbis-content-disp

Last Call on draft-yevstifeyev-http-headers-not-recognized - summarizing first week

Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC

LC comments on draft-yevstifeyev-http-headers-not-recognized-08.txt

link for subscribing HTTP streaming mailing list

LINK/UNLINK

Making 307 redirects permantent, Re: Issue 160 (Redirects and non-GET methods)

Meeting room change for HTTP streaming Bar BOF

Memento Internet Draft

Multiple Realm Authentication?

NEW ISSUE: message-body in CONNECT response

NEW: #225: PUT and DELETE invalidation vs. staleness

NEW: #235: Cache Invalidation only happens upon successful responses

P7: IANA registry for schemes (issue 141)

Pipelining hinting

Please Review my Internet-Draft

Proposal: 205 Bodies [#88]

repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02

Same Origin Policy and HTTP Authentication

TAG resolution on redirection with fragment identifiers

The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call)

The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02)

ticket #78 (Relationship between 401, Authorization and WWW-Authenticate)

TICKET 259: 'treat as invalid' not defined

Ticket 260: multiple disposition types, was: Comments on draft-ietf-httpbis-content-disp

Ticket 262: Discuss whether percent-decoding should also be done by receivers.

treating invalid parameters in Content-Disposition

Unifying & standardizing X-Moz & X-Purpose headers

Updated Content-Disposition error handling proposal on the wiki

WGLC for draft-ietf-httpbis-content-disp ?

Which headers to apply from a PUT request (Link?)

workability (or otherwise) of HTTP upgrade

Working Group Last Call: Content-Disposition

Working Group Last Call: draft-ietf-httpbis-content-disp-02

WWW-Authenticate / Proxy-Authenticate with 200 response

Ликвидация предприятий (по всей Украине )

Last message date: Friday, 31 December 2010 06:12:45 UTC