Re: Running cl-http under mac osx
Jerome Thomere <[email protected]>
| Newsgroups | gmane.lisp.cl-http |
|---|---|
| Message-ID | <[email protected]> |
In /etc/httpd/http.conf you can edit the following lines: # Port: The port to which the standalone server listens. For # ports < 1023, you will need httpd to be run as root initially. # Port 80 # I once change Port 80 to 81 and it didn't pose any problems. Jerome On Wednesday, April 2, 2003, at 04:16 PM, Christopher Eliot wrote: > Of course it is possible to run CL-HTTP on port 80, > but I'm not sure it would be worth the challenge. > > There is complex coordination between the Mac part of OS X > and the Unix part of it. It's all configurable, but Apple > clearly expects Apache to be the web server on port 80. > > You would be continually fighting to keep this configuration > operational, I think. Normal system updates would probably > break it four times a year or more. > > I think it would be easier to let Apple/Apache have port 80. > You could configure Apache to redirect all or most of its > services to CL-HTTP. You could also try to figure out how > to use one of the connectors that are used to make apache > talk to a servlet engine (modjk or warp). This would be > the "proper" method although I've never made it work. > > > On Wednesday, April 2, 2003, at 05:43 PM, John C. Mallery wrote: > >> At 15:56 -0500 4/2/03, Bruno Emond wrote: >>> I have downloaded the last version of cl-http (cl-http-70-159-devo). >>> >>> It seems that the only way to have cl-http running under MacOs X >>> (10.2.4) is >>> to set the port to something else than 80 (let's say 8080). >> >> If you run as root, I would imagine that you can serve port 80, but >> this might not be the safest way. Otherwise, you'll need to figure out >> how to tell mac os to use cl-http rather than it's built in web >> server >> for port 80. >> >> >>> >>> This is the error I get: >>> >>> Error in process HTTP Listener (80): UNAUTHORIZED-CLIENT-ACCESS: >>> Unauthorized client access. Permission denied. >> >> You'll probably going to need to debug this one. >> >>> >>> I also get the following error on the proxy start up: >>> >>> Error in process HTTP Listener (8000): OPENTRANSPORT-ERROR: Generic >>> OpenTransport error. Address already in use. >> >> I don't have any problem running the proxy on port 8000 >> >>> >>> >>> Any suggestions on how to configure OSX or cl-http to get rid of >>> these >>> errors ? >> >> >> >>> >>> Thanks >>> >>> Bruno >> >> > Prof. Christopher Eliot > Department of Computer Science > University of Massachusetts, Amherst > [email protected] >