Thanks :) But I'd rather get the exact version they are running since many different version of CP 2.1 are returning that header value.
It could be CP 2.1 beta, rc1 or final, actually we only switched the response header a few days after 2.1 final meaning there was a few days where the trunk was still using 2.1.0 when we were actually running a trunk version. But anyway good point :) (side note which has nothing to do with the current pb. CherryPy supports the OPTIONS request method which could be quite interesting in some places in TG to help user agents knowing whether or not a resources can handle a particular HTTP method). - Sylvain Selon Gábor Farkas <[EMAIL PROTECTED]>: > > Sylvain Hellegouarch wrote: > > > >>anyway, they're saying that they fixed it already... would be > >>interesting to know what threading problem they fixed, and how they > >>configured the cherrypy server... > > > > > > Indeed along with which version of CP they are using and whether or not > they are > > using the default WSGI server or another one. > > from the HTTP headers of diggdot.us: > > Server: CherryPy/2.1.0 > > :) > > gabor > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
