wxs's questions

I've put Amazon's API gateway in front of an existing HTTP API. That API has its own logging that needs access to the source IP address, however I can't seem to map the source IP to an X-Forwarded-For header in the Integration Request tab of the dashboard.

The API gateway docs mention $context.identity.sourceIp, but that only seems to be available in body templates. In my case I am trying to just directly map queries to the backend HTTP API so I don't have a body template.

The HTTP Headers settings in the Integration Request page won't accept the $context variable, sadly, giving the error:

Invalid mapping expression specified: Validation Result: warnings : [], errors : [Invalid mapping expression specified: $context.identity.sourceIp]

and claims to only be able to access HTTP headers from the request, query string parameters from the request, or path parameters from the request.

Is this actually impossible in the API gateway? Seems like this would be a very standard issue when wrapping an existing HTTP API.

Every once in a while when I'm debugging some web app, it would be useful for me to be able to serve a folder via a lightweight HTTP server. Something along the lines of

cd folder
httpserve -p 5000

in order to serve that folder over port 5000. Is there any tool to allow me to do this?

Thanks.

We have a Linux server with a couple of NFS shares on our local network, and we want to be able to access the data on those shares from some remote machines outside of the LAN. What we are planning on doing is an cron job on the remote machines triggering rsync to keep the folder up to date.

Just wondering if there's some sort of less "hacked-together" solution, something along the lines of an NFS-mount but optimized for high-latency connections.

We're in a mostly Linux environment, so Linux-only solutions are fine, although of course something that would work cross-platform is always nice.

Thanks!