Commas are now used by default in this case,
cheers, Sergey
On Tue, Sep 14, 2010 at 8:24 PM, Obele, Azubuko <
azubuko.ob...@morganstanleysmithbarney.com> wrote:
> The CacheControlHeaderProvider class separates the various cache-control
> headers with a semi-colon. My reading of the HTTP 1.1 spec
che-Control: dir1; dir2' into 'Cache-Control: dir1
>> Cache-Control: dir2'. It doesn't handle header parameters separated by
>> semi-colons well.
>>
>> -Original Message-
>> From: Obele, Azubuko (GWMG Technology)
>> Sent: Tuesday, Sept
> -Original Message-
> From: Obele, Azubuko (GWMG Technology)
> Sent: Tuesday, September 14, 2010 3:24 PM
> To: users@cxf.apache.org
> Subject: CacheControlHeaderProvider uses semicolons instead of commas
>
> The CacheControlHeaderProvider class separates the various cache-
parameters separated by
semi-colons well.
-Original Message-
From: Obele, Azubuko (GWMG Technology)
Sent: Tuesday, September 14, 2010 3:24 PM
To: users@cxf.apache.org
Subject: CacheControlHeaderProvider uses semicolons instead of commas
The CacheControlHeaderProvider class separ
The CacheControlHeaderProvider class separates the various cache-control
headers with a semi-colon. My reading of the HTTP 1.1 spec and pretty much any
example that turns up on Google suggests that commas should be used to separate
the various cache-control headers. Is this a bug?
Thanks,
