Skip to content
This repository has been archived by the owner on Mar 25, 2022. It is now read-only.

Nginx timeouts #104

Merged
2 commits merged into from
Oct 23, 2015
Merged

Nginx timeouts #104

2 commits merged into from
Oct 23, 2015

Conversation

ghost
Copy link

@ghost ghost commented Oct 23, 2015

commit 3dbe4de
Author: Lars Gierth larsg@systemli.org
Date: Fri Oct 23 04:56:54 2015 +0200

ipfs: make timeouts less likely

License: MIT
Signed-off-by: Lars Gierth <larsg@systemli.org>

commit 4b9dea8
Author: Lars Gierth larsg@systemli.org
Date: Fri Oct 23 05:00:17 2015 +0200

gateway: don't fall back to other gateways for too long

License: MIT
Signed-off-by: Lars Gierth <larsg@systemli.org>

Lars Gierth added 2 commits October 23, 2015 04:56
License: MIT
Signed-off-by: Lars Gierth <larsg@systemli.org>
License: MIT
Signed-off-by: Lars Gierth <larsg@systemli.org>
@ghost ghost added the solarnet label Oct 23, 2015
ghost pushed a commit that referenced this pull request Oct 23, 2015
@ghost ghost merged commit ba1be21 into master Oct 23, 2015
@ghost ghost deleted the nginx-timeouts branch October 23, 2015 03:00
@RichardLitt RichardLitt mentioned this pull request Oct 23, 2015
35 tasks
@jbenet
Copy link
Member

jbenet commented Oct 27, 2015

would this suck if we get DOSed then? or would a request fail early if the ipfs node drops the request (or is down)?

@ghost
Copy link
Author

ghost commented Oct 27, 2015

It doesn't make it a lot worse than it already is, I suppose. If I wanted to bring down solarnet, I'd go through port 4001 :)

There might be a few things we can do in the gateway code to make it more resilient, e.g. have it check client connection status regularly (client = nginx), and abort actions which originated from a dead connection.

This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant