|
Re: Why MD5 Headers are Imperative: msg#00449network.syndication.atom.protocol
+1. Eric: I think you're making this stuff *way* too difficult. - James Paul Hoffman wrote: > > At 4:53 AM +0000 8/17/06, Eric J. Bowman wrote: >> So let's extend HTTP 1.1 >> with an APP-specific header, for example when requesting the Member >> resource >> an APP client MUST send "X-APP-MD5:GET" AND "max-age:0". An APP-aware >> server >> MUST return VARY:X-APP-MD5 and a Content-Md5 header. > > -1. This is vast overkill, as shown by other responses on this thread. > > |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Why MD5 Headers are Imperative: 00449, Tim Bray |
|---|---|
| Next by Date: | Media resources in an entry with APP: 00449, Ben Bangert |
| Previous by Thread: | Re: Why MD5 Headers are Imperativei: 00449, Paul Hoffman |
| Next by Thread: | Re: Why MD5 Headers are Imperative: 00449, Eric J. Bowman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |