127.0.0.1 - - [18/May/2009:22:35:25 -0400] "GET /filestore/
retrieve_file.html?
fid=1335eaad7df0e63263c415be4061c8e34147e5e1&params=max|1 HTTP/1.0"
200 2961 "-" "ApacheBench/2.0.40-dev"
70.42.66.10 - - [18/May/2009:22:39:13 -0400] "GET /filestore/
retrieve_file.html?
fid=1335eaad7df0e63263c415be4061c8e34147e5e1&params=max|1 HTTP/1.0"
200 2961 "-" "ApacheBench/2.0.40-dev"
10.50.45.87 - - [18/May/2009:22:40:02 -0400] "GET /filestore/
retrieve_file.html?
fid=1335eaad7df0e63263c415be4061c8e34147e5e1&params=max|1 HTTP/1.0"
404 0 "-" "ApacheBench/2.0.40-dev"
10.50.0.1 - - [18/May/2009:22:35:52 -0400] "GET /filestore/
retrieve_file.html?
fid=1335eaad7df0e63263c415be4061c8e34147e5e1&params=75x75|1 HTTP/1.1"
404 5 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
1.9.0.10) Gecko/2009042316 Firefox/3.0.10"

Hi, it seems like we get different results w/ the exact same setup
depending on how we connect to nginx/ php-fpm. Connecting on the
local box via 127.0.0.1 returns the correct result, an image of 2961
bytes and a 200. Checking it against the box's own ip address
(10.50.45.87) returns a 404 and a 0-byte file. Checking it through
our load balancer w/ a public ip also returns a 0 byte 404 response.
Checking it w/ Firefox (and Modify Headers) through the load balancer
also returns a 0b 404.

We get these results consistently based on those test cases, and there
doesn't seem to be any rhyme or reason to it. Keepalives are on in
each case. It's not based on IP, since the same IP checked different
ways has different results. It's not based on browser or HTTP/1.0 vs.
HTTP/1.1 either.

It's not (as far as I can tell) allowed_clients, which is currently
this:
<value
name="allowed_clients">127.0.0.1,10.50.0.1,10.50.200.1,10.50.45.87</
value>
...and so should allow any of our potential clients (for this test) to
connect successfully.

I'm running out of ideas. Does anyone else have any?

Thanks,
Nicholas