The wiki is down, so I post it here first… #pragma section-numbers off
== Abstract == Use the Content-Disposition header to allow a client to request that a string be included in a new entry's URI == Status == Proposal (ThomasBroyer) == Rationale == Many existing weblog software implementations allow clients to request specific URI content entries. APP should also support this capability In addition to PaceMinimalSlug capabilities, the Content-Disposition header can be used when POSTing to Media Collections. == Proposal == 8.1.3 The Content-Disposition header When posting an atom:entry to a collection in order to add a new member, a client may include a Content-Disposition header [RFC2183]. This constitutes a request by the client that the URI assigned to the new resource incorporate string provided in the value of the Content-Disposition's "filename" parameter. Server implementations MAY attempt to comply with the request. Server implementations are more likely to be able to incorporate requested strings if they are constructed with sensitivity to IRI syntax rules [RFC3987]. In particular, strings containing characters with syntactic significance, in particular the path-separator character "/", are apt to cause server implementations difficulty. Servers MAY ignore the disposition value and any parameter other than the "filename" parameter. Servers SHOULD be prepared to process a header value encoded according to RFC2184 conventions for long values or charset encodings. This specification assigns no significance to the Content-Disposition header during a PUT request. Servers SHOULD ignore the header in such a situation and MUST not fail with a 501 (Not Implemented) status code solely because of the presence of the Content-Disposition header. == Impacts == == Notes == -- Thomas Broyer
