Re: [users@httpd] port forwarding and other options for having access to my apache server through the ip address

[angel Hall-Coulston]

Hi, 
Also be very careful that you are not breaching the Terms of your ISP. They for 
obvious reasons don’t allow just anybody to serve websites or other files…. You 
have to have permission as they WILL find you out and if it’s against terms, 
they could block you… 
It’s ALWAYS best to have a static IP assigned for stability…
Don’t want to be a spoilsport, just giving fair warning !

> On 11 Jan 2019, at 22:19, John  wrote:
> 
> I'm not sure about your configuration so this might be irrelevant, but try 
> looking at all the moving parts here.
> 
> For example, since your IP is dynamic, how are you doing address resolution 
> on the Internet? Does your 
> address resolver have the correct real address? Try pinging yourself.
> 
> If that works, then see where the router is sending port 80. The internal 
> router is probably a NAT arrangement,
> so check that the port 80 destination setting is for your server machine. 
> (ie, suppose you are at Inet address 
> 205.100.1.1, and that you can really ping this address. Where does the router 
> send port 80 to?) It should
> be something like 192.168.1.xxx. Is this your local server's address? If DHCP 
> it could easily change periodically.
> If so. make the internal address static.
> 
> If your actual firewall doesn't support static NAT addresses, you can usually 
> force the issue by giving the server 
> a static address that it will always use to connect.
> 
> If all that works, then look at the firewall router's log. Most of them 
> retain a log of connections and failed
> connections. See if your attempt to connect actually made it to your firewall 
> and how it disposed of it, One
> comment, these logs are about as arcane as anything I have ever seen!
> 
> Be careful, when you change settings you can make a real mess if you guess 
> wrong! Be sure you know what
> you did so you can back out without having to re-initialize.
> 
> Just as a last desperate idea, when you make a firewall/router change, power 
> cycle it, just in case the change
> didn't get picked up.
> 
> After that, sorry, off of ideas.
> 
> John
> =
> On Fri, 2019-01-11 at 14:23 -0700, Jonathon Koyle wrote:
>> The only other suggestions I have are to Verify that your server is 
>> accessible from another machine, not blocked by a firewall or only listening 
>> on loopback.  It isn't likely to be an ISP issue unless they try to restrict 
>> you from serving a website...
>> 
>> On Fri, Jan 11, 2019, 13:54 Stathis G. Arapostathis 
>> mailto:e.arapostat...@gmail.com> wrote:
>>> well, i have a dynamic ip but this is not my problem. I also portforwarded 
>>> port 80 before sending current question but I still do not have access. 
>>> 
>>> There are some years passed since the last time I port-forwarded apache 
>>> server and I thought that maybe some additional modifications from 
>>> apache-server side are needed as the updates pass through time.
>>> 
>>> I guess I have to contact my ISP again, it could be an ISP issue.
>>> thank you very much for the quick responses.   
>>> 
>>> 
>>>  
>>> 
>>> Virus-free. www.avast.com 
>>> 
>>>  
>>> On Fri, Jan 11, 2019 at 10:37 PM Jonathon Koyle >> > wrote:
 You may also need to look into whether you have a static or dynamic IP 
 address.  Many Consumer ISP packages provide dynamic, so the public IP 
 address changes periodically, often a day or two in my experience.  Also 
 note this won't be the IP address of your host machine, but the IP 
 assigned to the router.
 
 On Fri, Jan 11, 2019 at 11:14 AM John >>> > wrote:
> Start here:
> 
> https://portforward.com/technicolor/td5130/ 
> 
> 
> What you need to do is open port 80 (unencrypted http), that is, Internet 
> browsers. Be sure 
> you have appropriate security because you are putting your machine in a 
> hostile environment!
> If you don't believe that, look at your log after a few days on the 'net!
> 
> If you plan to encrypt your pages, you will also need port 443 open 
> (HTTPS).
> 
> Good luck.
> 
> John
> 
> 
> On Fri, 2019-01-11 at 20:04 +0200, Stathis G. Arapostathis wrote:
>> Dear Sirs / Madams,
>> 
>>   I was wondering on how I could configure my router and make any other 
>> necessary configurations in order to open up my localhost to the web and 
>> letting internet users to access my locally stored pages by putting my 
>> ip address.
>> 
>> I have an old router and no support is available. My isp does not have 
>> support and I re

[users@httpd] Updating Response url from Apache

[Naveen Nandyala]

Hello Team,


We are currently using application internal to our network 
using something like below
www.internal.com//menu.jsp

We are working to expose our application to external users we use an additional 
component Adobe Experience manager for accessing application which appends and 
additional context root in request header before even hitting our proxy server 
in DMZ which proxies request to internal.
Now our request for external users will be.
www.external.com/services/app//menu.jsp,
 when it redirects to internal Apache web server and when internal web server 
responds back to external its not appending additional context root in header 
/services/app due to which it's failing.

I’m looking for my internal Apache web server to identify any request coming to 
the internal Apache web server from www.external.com sends a response back to 
external by appending /services/app to the header before 
Application_context_Root.

I think I may not be able to use rewrite module to achieve, I’m looking at 
substitute module. Is there a way I can add a condition to substitute module 
and append it to response header from apache?

Any request that comes to Apache from www.external.com 
or Proxy server should be filtered and in every response that apache sends to 
this requests  I need to add “/services/app” to header before application 
context root.



Naveen Reddy
Senior Systems Engineer Middleware Webservices – Cloud Middleware
Strati PaaS – Core Foundations
Cell: 479 321 4679
naveen.nandya...@walmart.com

[users@httpd] RE: Configuring reverse proxy

[Muggeridge, Matt]

?  But first I want to ask if Apache needs to be able to see my external IP 
address.

That's ambiguous.  Is your 'external IP address' the publicly visible address 
that is used to access your website?  If so, then Apache will need to accept 
incoming connection requests on that IP address, naturally.


?  Ipconfig and other network applications can't see it.

Ok, so on windows, ipconfig will only see the addresses configured on your 
local machine.  So now your question about ipconfig mixed with external IP 
address is confusing to me.  If you believe the IP address is configured on 
your Windows machine and you're not seeing it with ipconfig, then can you ping 
that address from a different machine?  If so, then perhaps that address is 
configured on another machine in your network, yikes!


?  ; is this a good idea

I can't understand enough about what you're asking to comment.

Matt.

From: Osman Zakir [mailto:osmanzaki...@hotmail.com]
Sent: Saturday, 12 January 2019 9:16 PM
To: users@httpd.apache.org
Subject: [users@httpd] Configuring reverse proxy

I set up port forwarding on my router, so I think I'm ready to try this again.  
But first I want to ask if Apache needs to be able to see my external IP 
address.  Ipconfig and other network applications can't see it.  And my server 
app's executable is being allowed through the firewall currently; is this a 
good idea for when I want to set up a reverse proxy for it, or will it do?

[users@httpd] RE: Updating Response url from Apache

[Muggeridge, Matt]

There are bound to be other approaches, but one method is to configure the 
www.external.com server as a reverse proxy.  This assumes you have control of 
the web server running on www.external.com.

Matt.

From: Naveen Nandyala [mailto:naveen.nandya...@walmart.com.INVALID]
Sent: Monday, 14 January 2019 11:25 AM
To: users@httpd.apache.org
Subject: [users@httpd] Updating Response url from Apache

Hello Team,


We are currently using application internal to our network 
using something like below
www.internal.com//menu.jsp

We are working to expose our application to external users we use an additional 
component Adobe Experience manager for accessing application which appends and 
additional context root in request header before even hitting our proxy server 
in DMZ which proxies request to internal.
Now our request for external users will be.
www.external.com/services/app//menu.jsp,
 when it redirects to internal Apache web server and when internal web server 
responds back to external its not appending additional context root in header 
/services/app due to which it's failing.

I’m looking for my internal Apache web server to identify any request coming to 
the internal Apache web server from www.external.com 
sends a response back to external by appending /services/app to the header 
before Application_context_Root.

I think I may not be able to use rewrite module to achieve, I’m looking at 
substitute module. Is there a way I can add a condition to substitute module 
and append it to response header from apache?

Any request that comes to Apache from www.external.com 
or Proxy server should be filtered and in every response that apache sends to 
this requests  I need to add “/services/app” to header before application 
context root.



Naveen Reddy
Senior Systems Engineer Middleware Webservices – Cloud Middleware
Strati PaaS – Core Foundations
Cell: 479 321 4679
naveen.nandya...@walmart.com