4 ms·
Thanks, looks like it was at 1 per second...I just boosted it a bit. EDIT: boosted again...gosh, HN front page is no joke :D EDIT 2: I ran into multiple rate
by moksha256 6y ago
Thanks, looks like it was at 1 per second...I just boosted it a bit.
EDIT: boosted again...gosh, HN front page is no joke :D
EDIT 2: I ran into multiple rate limits, some of which were harder to discover/configure than others. Site should be back again. Sorry.
- throwaway894345 6y agoSeems like the host is down altogether for me.
- read_if_gay_ 6y agoFor me too.
- deleted 6y ago[deleted]
- dom96 6y agoWhy have rate limiting at all? Just disable it
- sangnoir 6y agoMaybe they don't have an unlimited budget for bandwidth charges? I'd strongly recommend they go behind a (free or cheap) caching CDN first before removing limits.
- doublerabbit 6y agoHost pings, but port 80 is dead.
- calibas 6y agoAlso, the rate limiting is probably meant to be based upon the client's IP, not the proxy IP. Usually, the proxy adds the client IPs to the request headers and you can use those in Nginx rules.