Re: [users@httpd] Re: Server won't direct to Internal IP address

2023-01-06 Thread Larry Irwin (work)
Why not set up a secure shell tunnel from the device you're using when outside the LAN into the RasPi and tunnel to 192.168.1.194 on whatever port you need. Then connect to 127.0.0.1:{tunnel_port} on the device. I do this with PuTTY all the time so I can use a single port forward and have publi

[users@httpd] RE: httpd 2.4.x mod_md module MDContactEmail Directive - does that directive permit more than one email address

2023-01-06 Thread paul.leo
Thanks Christophe. Appreciate the response. -Original Message- From: Christophe JAILLET Sent: Thursday, January 5, 2023 1:35 PM To: users@httpd.apache.org; paul@stgconsulting.com Subject: Re: httpd 2.4.x mod_md module MDContactEmail Directive - does that directive permit more than

[users@httpd] Re: Server won't direct to Internal IP address

2023-01-06 Thread 😉 Good Guy 😉
On 06/01/2023 10:05, jason kerr wrote: > The full message is. > > This site can’t be reached > 192.168.1.194 took too long to respond. Try: Checking the connection > ERR_CONNECTION_TIMED_OUT > > On Fri, 6 Jan 2023, 00:58 Frank Gingras, > wrote: > > That error

Re: [users@httpd] Server won't direct to Internal IP address

2023-01-06 Thread Luis Speciale
On 06/01/2023 11:14, Antony Stone wrote: On Friday 06 January 2023 at 11:05:42, jason kerr wrote: The full message is. This site can’t be reached 192.168.1.194 took too long to respond. So, that tells you that the *Raspberry Pi* is not trying to connect to the boiler on behalf of the brow

Re: [users@httpd] Server won't direct to Internal IP address

2023-01-06 Thread Antony Stone
On Friday 06 January 2023 at 11:05:42, jason kerr wrote: > The full message is. > > This site can’t be reached > 192.168.1.194 took too long to respond. So, that tells you that the *Raspberry Pi* is not trying to connect to the boiler on behalf of the browser, but is simply telling the browser

Re: [users@httpd] Server won't direct to Internal IP address

2023-01-06 Thread jason kerr
The full message is. This site can’t be reached 192.168.1.194 took too long to respond. Try: Checking the connection ERR_CONNECTION_TIMED_OUT On Fri, 6 Jan 2023, 00:58 Frank Gingras, wrote: > That error isn't helpful - show the full and unredacted error. Also, a > ping isn't a useful test. > >

[users@httpd] Apache dropping Content-Length header for HEAD responses where Content-Length is 0

2023-01-06 Thread Piotr Dobrogost
Hi, On freshly installed Apache 2.4.52 on Fedora with default configuration I'm observing that for HEAD response the Content-Length header is not being sent for empty files (it is present for non-empty files). When changing HEAD to GET the header is present for such files. Sidney Shek asked very s

Re: [users@httpd] Server won't direct to Internal IP address

2023-01-06 Thread Antony Stone
On Friday 06 January 2023 at 01:51:13, jason kerr wrote: > I can access the Apache web server when internally on the LAN and use the > boiler control page, however I can't get the boiler control page to display > when accessing the webssever from an external IP. I can access the > webssever extern