487 reputation
316
bio website
location Bedford, United Kingdom
age
visits member for 3 years, 5 months
seen Aug 15 at 17:18

Aug
12
awarded  Notable Question
Jul
16
awarded  Popular Question
Jul
2
awarded  Curious
Nov
8
awarded  Popular Question
Sep
11
awarded  Popular Question
Jul
19
awarded  Popular Question
Jun
27
awarded  Popular Question
May
18
awarded  Popular Question
May
9
answered Nginx installed from apt-get - Do I need to create my own user?
Mar
28
answered Postfix - do not list domain example.com in BOTH mydestination and virtual_alias
Mar
19
awarded  Popular Question
Mar
8
awarded  Yearling
Dec
5
comment sudoers security
Sorry, I'm not following you. I'm not trying to mirror a repository. I'm updating working copies on multiple servers.
Dec
5
comment sudoers security
Hi Philippe, I'm happy to consider alternatives, but the restriction here is that the post-commit trigger is run as www-data. Having this user svn update locally is pretty standard, but I need a method of letting www-data update the remote server. The cli user has been setup solely for admin tasks between servers in the cluster, so ssh uses public/private keys and is restricted to the local subnet.
Dec
5
asked sudoers security
Oct
26
accepted Logging the client IP with Nginx/Varnish/Apache
Oct
26
comment Logging the client IP with Nginx/Varnish/Apache
Note to self: Don't skim-read code! Thanks Shane. It makes perfect sense now.
Oct
25
comment Logging the client IP with Nginx/Varnish/Apache
So with the default logic, for non-Nginx traffic, X-Forwarded-For is set to the client IP, and is used by mod_rpaf correctly? For Nginx traffic, X-Forwarded-For would look like '127.0.0.1, 1.2.3.4'? The mod_rpaf documentation states: "...if there is an incoming X-Forwarded-For header and the proxy is in it's list of known proxies it takes the last IP from the incoming X-Forwarded-For header and changes the remote address of the client in the request structure", so now I'm confused why the default VCL logic isn't working in my scenario.
Oct
24
comment Logging the client IP with Nginx/Varnish/Apache
Varnish is used for in-memory caching of static content and load balancing for the back-end servers. I'm not saying that some or all of this couldn't be done in Nginx alone, but other than the logging, it's working very well as is.
Oct
24
asked Logging the client IP with Nginx/Varnish/Apache