108 reputation
6
bio website docx4java.org
location New South Wales
age
visits member for 2 years, 8 months
seen Nov 25 at 7:30

I maintain the docx4j project, an ASLv2 Java library for manipulating Microsoft OpenXML packages (docx/pptx/xlsx) using JAXB.


Dec
10
awarded  Popular Question
Sep
24
awarded  Autobiographer
May
13
awarded  Student
May
12
comment my IP address is different to remote address at EC2
I agree with your conclusion that EC2 has nothing to do with it (except insofar as it sees things a little differently). Surprisingly, what is my IP gives the same result for both http and https/SSL - different to what EC2 sees. I'll post a question on whirlpool to see what people know about what Telstra is doing, and report back...\
May
12
comment my IP address is different to remote address at EC2
No, just straight in. I should say that reverse IP lookup services say that the IP address IP2 belongs to Telstra (my local ISP), so this isn't an IP address EC2 is allocating. The question is how/why is EC2 seeing a different address to other sites? I guess it is possible that Telstra has some logic which handles connections to EC2 differently to connections to other sites...
May
12
comment my IP address is different to remote address at EC2
That reveals the same source IP as I see in my access logs - different from the various "what is my IP" services.
May
12
comment my IP address is different to remote address at EC2
Australia; Telstra mobile broadband; lagado.com/proxy-test says my request doesn't appear to have come from a proxy (although there probably is, but still why would the box at EC2 see things differently?). Connection to the server is via plain old GET requests in a web browser (Chrome or whatever). Host is in EC2 eu-west.
May
12
asked my IP address is different to remote address at EC2
May
11
awarded  Scholar
May
11
awarded  Supporter
May
11
accepted preventing squid forwarding loop with IPtables
May
11
comment preventing squid forwarding loop with IPtables
Great suggestion. That worked nicely, thank you! I also needed iptables -t nat -A OUTPUT --src 0/0 -p tcp --dport 80 -j REDIRECT --to-port 8080. Now to get the client to respect the 413 response...
May
11
awarded  Editor
May
11
revised preventing squid forwarding loop with IPtables
Server is running on Amazon EC2
May
11
comment preventing squid forwarding loop with IPtables
Thanks for the reply; I did try "-i eth0"; I probably should have included that in the question. I'm not explicitly telling squid what upstream server to use. It seems to know that from the incoming HTTP request.
May
11
asked preventing squid forwarding loop with IPtables
Jun
5
comment Why does EC2 instance have problems upgrading my Ubuntu server to 12.04?
11.10 to 12.04 LTS worked for me, via SSH connection.