-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not work #62
Comments
Same issue here. The connection works in a way because it correctly detects if there is a file or not (404), but when there is, this message appears, leading to a "no data received" issue |
+1,How fix it? |
3 years later : no idea. I finally dropped GridFS, whick lack support. I encourage you to do the same and look for alternatives. |
thank you,I originally wanted to use mongodb's GridFS as an object store. But I just found a good solution |
GET http://127.0.0.1/images/5397f74005fbed25453660a3 net::ERR_EMPTY_RESPONSE
user nobody;
worker_processes 1;
error_log logs/error.log;
error_log logs/error.log notice;
error_log logs/error.log info;
pid logs/nginx.pid;
worker_rlimit_nofile 51200;
events {
use epoll;
worker_connections 51200;
}
http {
include mime.types;
default_type application/octet-stream;
}
error.log
2014/06/11 15:42:34 [error] 22179#0: *7 Mongo connection dropped, could not reconnect, client: 127.0.0.1, server: localhost, request: "GET /images/5397f74005fbed25453660a3 HTTP/1.1", host: "127.0.0.1"
2014/06/11 15:42:34 [alert] 22179#0: *7 header already sent, client: 127.0.0.1, server: localhost, request: "GET /images/5397f74005fbed25453660a3 HTTP/1.1", host: "127.0.0.1"
The text was updated successfully, but these errors were encountered: