How to interpret Cache-Control: no-cache="Set-Cookie"

Hi,

Dean Gaudet of HotWired pointed this out. From RFC2068:

          cache-request-directive =
                            "no-cache" [ "=" <"> 1#field-name <"> ]

...

   When a directive appears without any 1#field-name parameter, the
   directive applies to the entire request or response. When such a
   directive appears with a 1#field-name parameter, it applies only to
   the named field or fields, and not to the rest of the request or
   response. This mechanism supports extensibility; implementations of
   future versions of the HTTP protocol may apply these directives to
   header fields not defined in HTTP/1.1.

How do we interpret Cache-Control: no-cache="Set-Cookie":
- this page is OK to cache, just strip out the Set-Cookie headers?
- this page is OK to cache, keep the Set-Cookie headers? This would
  serve up the same cookie to many browsers.

This is a sample header:

HTTP/1.1 200 OK
Date: Sat, 12 Apr 1997 07:53:23 GMT
Server: Apache/1.2b9-dev HotWired/1.2
Set-Cookie: p_uniqid=z80NpOIBc1mlzSL+LA; path=/; domain=.wired.com; expires=Fri, 31-Dec-99 23:59:59 GMT
Set-Cookie: s_uniqid=z80NpOIBc1mlzSL+LA; path=/; domain=.wired.com
Cache-Control: no-cache="Set-Cookie"
Set-Cookie: p_uniqid=z80NpOIBc1mlzSL+LA; path=/; domain=.wired.com; expires=Fri, 31-Dec-99 23:59:59 GMT
Set-Cookie: s_uniqid=z80NpOIBc1mlzSL+LA; path=/; domain=.wired.com
Cache-Control: no-cache="Set-Cookie"
Connection: close
Content-Type: text/html

-- 
miguel a.l. paraz  <map@iphil.net>                              +63-2-893-0850
iphil communications, makati city, philippines          <http://www.iphil.net>