Reputation
449
Top tag
Next privilege 500 Rep.
Access review queues
Badges
3 10 31
Impact
~241k people reached

  • 0 posts edited
  • 0 helpful flags
  • 32 votes cast
Jan
26
awarded  Popular Question
Sep
26
comment Apache2.4/nginx - route all traffic to requesting host?
This is on an intranet not connected to the internet. If any machine on the network is compromised, there are much bigger problems than this that need fixing. Only a few people will ever use this, and REMOTE_ADDR seems like the better way to go anyway.
Sep
26
comment Apache2.4/nginx - route all traffic to requesting host?
This isn't for the public internet; this is specifically to support local development, and it's HTTP/S only.
Sep
26
accepted Apache2.4/nginx - route all traffic to requesting host?
Sep
25
revised Apache2.4/nginx - route all traffic to requesting host?
edited tags; edited title
Sep
25
comment Apache2.4/nginx - route all traffic to requesting host?
Preferably I could grab the incoming IP, like I mentioned. That would be a bit easier for myself and others who may use this than the xip.io solution of routing to the prefix in the domain. But either solves my technical issue and I could live with the slight degradation in functionality.
Sep
25
comment Apache2.4/nginx - route all traffic to requesting host?
@MichaelHamptonhere is no "problem itself." The problem is that certain services only accept requests from certain domains, and my specific problem requires that a handful of subdirectories go one place, and all other traffic go elsewhere. It's not a good server setup, and I'm not defending it. What I'm saying is that the problem statement is accurate, and I have more of a chance of winning the lottery than addressing the underlying problem -> these services don't work locally or from external domains. I don't control them. I need xip.io on my intranet.
Sep
25
revised Apache2.4/nginx - route all traffic to requesting host?
added 162 characters in body
Sep
24
comment Apache2.4/nginx - route all traffic to requesting host?
I'm using internal infrastructure for a number of services, and the only way to get it to work is https and getting cookies from a different domain. IPs change dynamically. I could also get by with 10.113.12.10.server.com routing to 10.113.12.10, if that's easier.
Sep
24
asked Apache2.4/nginx - route all traffic to requesting host?
Sep
18
asked Apache adding newline to SSI include
Aug
2
awarded  Notable Question
Jun
10
comment Apache2 LocationMatch allow an index for login but nothing else?
That seems to match the opposite of what I need.
Jun
10
asked Apache2 LocationMatch allow an index for login but nothing else?
May
5
awarded  Nice Question
Mar
18
awarded  Yearling
Jan
5
awarded  Famous Question
Dec
24
awarded  Popular Question
Sep
12
awarded  Popular Question
Jul
2
awarded  Curious