Yes! I added
tools.encode.encoding = "utf-8" to the global section of my app.cfg and success! I haven't seen any of those dreaded 408 errors yet. CherryPy 3.2 seems to work nicely now. I'll inform anyone if I find any other issues. Thanks -Sam On Jan 7, 4:28 pm, Daniel Fetchinson <[email protected]> wrote: > > Right now it's being rendered by the browsers as "Â" (without quotes). > > > That's because it's telling the browser the wrong encoding. > > > The best reference I can find is: > >http://stackoverflow.com/questions/1461907/html-encoding-issues-a-cha... > > > So how do I tell CherryPy to tell the browser that it's utf-8? > > Is this what you are looking > for?http://www.cherrypy.org/wiki/BuiltinTools#tools.encode > > Cheers, > Daniel > > > > > > > > > > >> What makes you think will be rendered differently if the > >> charset is changed? I'd think in both cases it will show up as a > >> non-breaking space. > > >> Cheers, > >> Daniel > > >> -- > >> Psss, psss, put it down! -http://www.cafepress.com/putitdown > > > -- > > You received this message because you are subscribed to the Google Groups > > "TurboGears" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/turbogears?hl=en. > > -- > Psss, psss, put it down! -http://www.cafepress.com/putitdown -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
