[Tickets #9435] Re: no utf encoding when subscribing to a remote calendar

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9435
------------------------------------------------------------------------------
  Ticket             | 9435
  Updated By         | karagian at gmail.com
  Summary            | no utf encoding when subscribing to a remote calendar
  Queue              | Kronolith
  Version            | 2.3.5
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


karagian at gmail.com (2010-12-30 08:51) wrote:

I played with several options in the apache configuration  
(AddDefaultCharset, AddCharset) in order to force apache to serve the  
response in the correct encoding (utf-8). While this works for files  
stored on the local filesystem (a simple text .ics file), it doesn't  
affect the php's response produced by kronolith.
So, just to clarify your previous response, when you do the test with  
the 2 requests (one with an Accept-Charset header and one without) you  
still get the same valid UTF-8 encoded response? That shouldn't be  
happening...
I think that by default an HTTP text/* response is ISO-8859-1 and not  
UTF-8, unless otherwise specified.  
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7.1)
What I'm trying to say is that the request generated by kronolith  
should specify an Accept-Charset header in order to get the correct  
response from the server.

Thank you for everything and I wish you all a happy New Year :)