Just ignore this advice, you'd be better of just using
ResponseBuilder.header(String, Object) method instead of using CacheControl
utility :
builder.header("Cache-Control", "dir1, dir2");
The approach I suggested can be handy in a number of cases, but it's an
overkill for this one...
cheers, Sergey
On Wed, Sep 15, 2010 at 9:40 PM, Sergey Beryozkin <[email protected]>wrote:
> Hi
>
> If you need to have commas instead of semi-colons, then you may want to try
> using ResponseHandler filter as a workaround, where you can replace Response
> with the new one, and replace all ";" in the Cache-Control value along the
> way; I'd need to introduce a contextual property later on to ensure commas
> and semi-colons can be dealt with, similarly to the way cookies are dealt
> with
>
> cheers, Sergey
>
>
> On Tue, Sep 14, 2010 at 8:37 PM, Obele, Azubuko <
> [email protected]> wrote:
>
>> Actually, this seems to be an IE6 bug. (Googling around turns up this
>> http://www.webdeveloper.com/forum/showthread.php?t=45934 among others).
>> IE6 doesn't transform 'Cache-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, September 14, 2010 3:24 PM
>> To: [email protected]
>> Subject: CacheControlHeaderProvider uses semicolons instead of commas
>>
>> 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,
>>
>> --------------------------------------------------------------------------
>> Important Notice to Recipients:
>>
>> It is important that you do not use e-mail to request, authorize or effect
>> the purchase or sale of any security or commodity, to send fund transfer
>> instructions, or to effect any other transactions. Any such request, orders,
>> or instructions that you send will not be accepted and will not be processed
>> by Morgan Stanley Smith Barney.
>>
>> The sender of this e-mail is an employee of Morgan Stanley Smith Barney
>> LLC. If you have received this communication in error, please destroy all
>> electronic and paper copies and notify the sender immediately. Erroneous
>> transmission is not intended to waive confidentiality or privilege. Morgan
>> Stanley Smith Barney reserves the right, to the extent permitted under
>> applicable law, to monitor electronic communications. By e-mailing with
>> Morgan Stanley Smith Barney you consent to the foregoing.
>>
>> --------------------------------------------------------------------------
>> Important Notice to Recipients:
>>
>> It is important that you do not use e-mail to request, authorize or effect
>> the purchase or sale of any security or commodity, to send fund transfer
>> instructions, or to effect any other transactions. Any such request, orders,
>> or instructions that you send will not be accepted and will not be processed
>> by Morgan Stanley Smith Barney.
>>
>> The sender of this e-mail is an employee of Morgan Stanley Smith Barney
>> LLC. If you have received this communication in error, please destroy all
>> electronic and paper copies and notify the sender immediately. Erroneous
>> transmission is not intended to waive confidentiality or privilege. Morgan
>> Stanley Smith Barney reserves the right, to the extent permitted under
>> applicable law, to monitor electronic communications. By e-mailing with
>> Morgan Stanley Smith Barney you consent to the foregoing.
>>
>
>
