Re: Apache Server Question

[Patrik Schindler <poc@xxxxxxxxxx>]

Hello Greg,

Am 05.01.2022 um 19:33 schrieb Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>:

> We have an Apache instance (for DB2 Web Query) that listens on 2 ports - one is for internal network users, the other is for external users coming in through a proxy server.
>
> My question is this... we would like for it to "stop listening" on the external port (i.e. deny access) unless it's Monday - Friday 8:00am to 5:00pm.

Not within the configuration file itself.

You can prepare two configuration files with different "Listen" parameters and stop/start the instance with the correct configuration file via a scheduled job. Then the proxy server will show error 500 to the world — not exactly something I want to see when I visit a website. It smells like some incompetent guy isn't able to administer his servers correctly.

If the proxy server is a Linux machine, it's probably better to switch configurations there with a cron job, and instead of stuff just not working, maybe show a local index.html with a nice logo and "access not allowed at this time".

I'm using a small shell script for some similar occasions. Some static websites are located on my venerable 150, being proxied to the world via Apache. But when the 150 is down for whatever reason, the shell script sees no connection possible to port 80, changes configuration files to use a Linux local copy, and reloads Apache to activate the config changes. Can send it to you if you're interested. I bet you can easily adopt it to reflect your requirements.

:wq! PoC