Ticket #291 (reopened defect)

Opened 2 years ago

Last modified 5 months ago

Unable to run TG on unix domain socket

Reported by: cliff@develix.com Assigned to: anonymous
Priority: normal Milestone: __future__
Component: Deployment Version:
Severity: normal Keywords:
Cc:

Description

It appears that due to a port check in startup.py and the fact that cherrypy checks to see if server.socketPort is set before checking for server.socketFile (which it appears TG does for you whether you want it to or not), it isn't currently possible to run TG on a local socket. If you are running TG behind another webserver such as Lighttpd, a socket would be the preferred way as it's faster and more secure.

Change History

09/22/06 11:24:42 changed by khorn

Can anyone verify that this is still a problem?

10/11/06 23:49:14 changed by max

  • status changed from new to closed.
  • resolution set to worksforme.

TurboGears correctly passes server settings to CherryPy?: 

2006-10-12 08:29:56,058 cherrypy.msg INFO CONFIG:   server.socket_port: 8080
2006-10-12 08:29:56,058 cherrypy.msg INFO CONFIG:   server.socket_file: /tmp/z01

CherryPy? then complains about "Port is busy" but I don't see this as TurboGears issue. I close this ticket for now; reopen if there is something need to be fixed with TG itself.

10/12/06 09:42:21 changed by jorge.vargas

  • status changed from closed to reopened.
  • resolution deleted.
  • milestone set to __future__.

actually if this is a CP problem we should report it to their trac and close this ticket ones that one is fix.

12/13/07 14:14:44 changed by khorn

Was this ever reported to the CherryPy? folks?

Is it even an issue in CP3 or only in CP2?