Re: post 8000

Hi,

This is how I started playing with ports:


First I modified /etc/httpd/httpd.conf:

LoadModule proxy_module       libexec/httpd/libproxy.so
[...]
AddModule mod_proxy.c
[...]
<IfModule mod_proxy.c>
	ProxyPass / http://192.168.1.49:8000/
	ProxyPassReverse / http://192.168.1.49:8000/
</IfModule>

and restarted apache:

$ sudo httpd restart

At this point, when I went to http://localhost/ apache would report:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.

Reason: Could not connect to remote machine: Connection refused

Next, I'd start lispworks and cl-http on the regular port 8000, and try

http://192.168.1.49

If there are still links being displayed with 8000 as the port, I'd  
try doing
(HTTP:DEFINE-URL-CONTEXT-REMAPPINGS (:http "192.168.1.49" 8000  
"192.168.1.49" 80))

Mark, how does this work with your site?

-- 
chr

On Feb 24, 2009, at 10:07 PM, Chun Tian (binghe) wrote:

> Hi, Mark
>
> In theory, try to enable following one line in  
> #p"http:examples;configuration.lisp" should work:
>
> (set-standard-http-port 80 :http)
>
> But the problem is that you may not have access to bind on port 80,  
> as a normal user on Mac OS X. Only port > 1024 is permitted. I  
> suggest three ways:
>
> 1) Run an Apache which ships with MacOS and bind on port 80, then  
> use Apache proxy module and rewrite module to rewrite the Apache  
> URL (on port 80) to CL-HTTP (on port 8000). (Most safe way I think)
>
> 2) Try to deliver your CL-HTTP applications into a standalone  
> console application, set CL-HTTP listen on port 80, then run it  
> with "sudo".
>
> 3) Just save-image your lispworks with (:environment nil), as a  
> console application, start LW from "sudo", then run a CL-HTTP in  
> it. (not safe if your CL-HTTP also open the Web Listener)
>
> On 2009-2-25, at 03:15, Mark Klein wrote:
>
>>
>> I'm on Mac OS 10.5.6, running cl-http 70.216 on Lispworks 5.0.2 on an
>> Intel duo-core.
>>
>> 	Mark
>>
>>> Mark,
>>> What OS are you serving from?
>>> -- 
>>> chr
>>>
>>> On Feb 24, 2009, at 7:51 PM, Mark Klein wrote:
>>>
>>>>
>>>> Is there a way to re-configure cl-http so it serves on the standard
>>>> port (i.e. so you don't have to specify the port in the domain  
>>>> name)
>>>> rather than port 8000? If so, how? I have some users who's firewall
>>>> blocks port 8000, so they can't use my system.
>>>>
>>>>   Thanks,
>>>>
>>>> 	Mark
>>>>
>>>> -----------------
>>>> Mark Klein
>>>> Principal Research Scientist
>>>> MIT Center for Collective Intelligence
>>>> http://cci.mit.edu/klein/
>
> --
> Chun Tian (binghe)
> NetEase.com, Inc.
> P. R. China
>


_______________________________________________
WWW-CL mailing list
[email protected]
https://lists.csail.mit.edu/mailman/listinfo/www-cl