Mário Gamito wrote:
>> Try to bind the Jabber HTTP interface to localhost and use apache as
>> proxy. Then you can use all kind of restrictions in your httpd.conf.
> I can't bind the Jabber HTTP to localhost.
>
> Any ideas ?
>
> I'm no Apache guru :(
Then why don't you use mod_proxy_http and re
Hi,
Try to bind the Jabber HTTP interface to localhost and use apache as
proxy. Then you can use all kind of restrictions in your httpd.conf.
I can't bind the Jabber HTTP to localhost.
Any ideas ?
I'm no Apache guru :(
Warm Regards,
Mário Gamito
-
Mário Gamito wrote:
>> That would probably be completely dependent of the functions in your
>> Jabber server, since I assume that is responsible for serving those
>> ports?
>> If it uses Apache as it's web interface, just use .htaccess as normal.
> The Jabber server has no function for that and do
Hi,
That would probably be completely dependent of the functions in your
Jabber server, since I assume that is responsible for serving those ports?
If it uses Apache as it's web interface, just use .htaccess as normal.
The Jabber server has no function for that and doesn't use Apache's web
int
Mário Gamito skrev:
Hi,
I have this server with Apache 1.3.37, with mod_proxy.
Let's say http://www.domain.foo
In the same server, I have a Jabber server that has an HTTP admin
console in ports 9090 (HTTP) and 9091 (HTTPS).
Is it possible with apache to protect the URLs with those ports like
Hi,
I have this server with Apache 1.3.37, with mod_proxy.
Let's say http://www.domain.foo
In the same server, I have a Jabber server that has an HTTP admin
console in ports 9090 (HTTP) and 9091 (HTTPS).
Is it possible with apache to protect the URLs with those ports like if
it were done with
