Re: [users@httpd] make_sock: could not bind to address 0.0.0.0:8888

Hai jeff The map server and apache running on same machine. On Thursday 13 February 2014 11:37 PM, Jeff Trawick wrote: On Thu, Feb 13, 2014 at 6:13 AM, Varun Bhuvanendran mailto:varun.bhuvanend...@gmail.com>> wrote: This error appears when i tried to restart apache |(98)Address alre

[users@httpd] Re: Preventing an open proxy with both a single SSL virtual host and a non-SSL virtual host

Surely this is not that unusual a configuration - no? Do I maybe need a "default.only" type virtual host on the port 443 side too? Thanks again - Richard On Thu, Feb 13, 2014 at 12:16 AM, Richard Mixon wrote: > We've setup a new Apache server on Centos 6.4, httpd 2.2.15. > > The site is runnin

RE: [users@httpd] Rewrite all to DocRoot

I just realised that I need to exclude the perl directory so I can runs scripts in the index.html? -Original Message- From: Eric Covener [mailto:cove...@gmail.com] Sent: Friday, 14 February 2014 12:12 AM To: users@httpd.apache.org Subject: Re: [users@httpd] Rewrite all to DocRoot > On e

Re: [users@httpd] make_sock: could not bind to address 0.0.0.0:8888

On Thu, Feb 13, 2014 at 6:13 AM, Varun Bhuvanendran < varun.bhuvanend...@gmail.com> wrote: > This error appears when i tried to restart apache > > (98)Address already in use: make_sock: could not bind to address 0.0.0.0: > no listening sockets available, shutting down > > is the map server run

RE: [users@httpd] apache caching 400 http status?

>We had this problem too and so stopped using mod_disk_cache for a few months. >I was under the impression it had been fixed and so we've >recently turned it >back on. We're on Apache/2.2.26. I had it happen in mod_mem_cache also, it's triggered in the main mod_cache mod. Below is the releva

Re: [users@httpd] port redirecting mapping

It was so helpful. Thanks thomas On Feb 13, 2014 6:44 PM, "Thomas Eckert" wrote: > The problem with your vhost is that it responds to requests on port 80 and > if a request hits your server on port 3030 that vhost is simply not used. > That's what ** does. Can't help you with the Rewrite > stuff,

Re: [users@httpd] port redirecting mapping

The problem with your vhost is that it responds to requests on port 80 and if a request hits your server on port 3030 that vhost is simply not used. That's what ** does. Can't help you with the Rewrite stuff, I've kept my distance from it so far. You would need someone else to look over that, in ca

Re: [users@httpd] Rewrite all to DocRoot

> On each of these virtual hosts I want a request for any URI to be sent to the > document root default (/index.html or just /) > > What the best way to do this per virtual host? I usually use: AliasMatch ^(.*)$ /fspath/to/index.html -

[users@httpd] make_sock: could not bind to address 0.0.0.0:8888

This error appears when i tried to restart apache (98)Address already in use: make_sock: could not bind to address 0.0.0.0: no listening sockets available, shutting down I had a map server running at port . I tried to do a *Redirect* so that a direct access of the map server from remote i

[users@httpd] Rewrite all to DocRoot

Hi All I'm sure this is a very easy question but I want to make sure I get it right I have to run three virtual hosts on separate IP addresses for notification messages (the reason is due to how the network kit does the redirection of traffic) On each of these virtual hosts I want a request f

Re: [users@httpd] port redirecting mapping

Thomas This was what i am looking for. Thnaks thomas. what i was trying to do is, allow access to *http://domain_name *, if a request like *http://domain_name:3030 *comes it should be redirected/mapped to another link. From the above help i could redi

Re: [users@httpd] port redirecting mapping

I'm confused as to what your setup and intention is. From your original message I assumed you were talking about a "normal" server but your configuration example looks like a reverse proxy. Also, I assumed you wanted requests to http://domain_name:3030/ to be redirected but then you said *all* requ

Re: [users@httpd] Re: reverse proxy choice to origin servers: https->https or https->http

If you use httpd as reverse proxy then clients will perform SSL handshakes with your reverse proxy. In SSL there is no distinction between decrypting the HTTP headers only or decrypting the full HTTP request - it's simply "payload" and it will be decrypted as a whole. If you want to understand how