4 ms·
I can't believe you guys are debating the correct HTTP return code for a joke service? Besides, it's obviously 200.
by darkchasma 13y ago
I can't believe you guys are debating the correct HTTP return code for a joke service? Besides, it's obviously 200.
- talles 13y agoWait... is it a joke?
- Daviey 13y agoI hope not, I've been depending on this service for a while. I have it integrated via FUSE on my prod servers. We did have some problems of blocking on large files, which is less than ideal for a /dev/null service. After dealing with their customer support (which has been super helpful), we are looking to move to a named pipe / FIFO.. Which will non-block and cache lolcally, with a watcher service to push it to their site. Happy Customer, A+++, would recommend.
- einhverfr 13y agoThese provide great opportunities for better understanding return codes. Besides, for POST it is obviously 202 ACCEPTED
- deleted 13y ago[deleted]
- general_failure 13y agoWell with the planned dev/random support, this is going to kick ass.
- Spooky23 13y agoDoes it discard data in a manner compliant with FIPS 140-2? Or NIST SP800-88?