Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

1

It's usually better to allow clients to fail quickly, unless you have reason to think the failure is the result of some sort of malicious request. Allowing clients to hang until they time out can consume resources, frustrate users, etc., etc.

TomG
– TomG

2014-04-29 02:17:49 +00:00
Commented Apr 29, 2014 at 2:17
Actually you would be much better off letting bad request fail quickly -- hanging them creates a nasty ddos vector, web servers don't like stuck processes whereas clients can easily choose to fire and forget allowing them to create many, many hung processes. If you are looking at flood control or to prevent brute force attacks on secrets there are much better options.

Wyatt Barnett
– Wyatt Barnett

2014-07-25 13:22:56 +00:00
Commented Jul 25, 2014 at 13:22

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »