-
```
The official Content-Disposition spec in RFC 2183 does not allow non-ASCII
characters to be sent. It requires them to be encoded using an extended syntax
introduced in RFC 2184.
During HTTP com…
-
```
The official Content-Disposition spec in RFC 2183 does not allow non-ASCII
characters to be sent. It requires them to be encoded using an extended syntax
introduced in RFC 2184.
During HTTP com…
-
I sporadically had trouble extracting attachments from some received mails, which when checked do work in GMail. After analysis, I traced it down to extraneous whitespace in the Content-Disposition he…
-
```
What steps will reproduce the problem?
1. Do a POST to a URL with multiple copies of a parameter with the same name,
but different values. Example:
usernames=itchy
usernames=scratchy
2. Observe i…
-
```
What steps will reproduce the problem?
1. Do a POST to a URL with multiple copies of a parameter with the same name,
but different values. Example:
usernames=itchy
usernames=scratchy
2. Observe i…
-
```
What steps will reproduce the problem?
1. Do a POST to a URL with multiple copies of a parameter with the same name,
but different values. Example:
usernames=itchy
usernames=scratchy
2. Observe i…
-
```
What steps will reproduce the problem?
1. Do a POST to a URL with multiple copies of a parameter with the same name,
but different values. Example:
usernames=itchy
usernames=scratchy
2. Observe i…
-
```
What steps will reproduce the problem?
1. Do a POST to a URL with multiple copies of a parameter with the same name,
but different values. Example:
usernames=itchy
usernames=scratchy
2. Observe i…
-
```
What steps will reproduce the problem?
1. Do a POST to a URL with multiple copies of a parameter with the same name,
but different values. Example:
usernames=itchy
usernames=scratchy
2. Observe i…
-
```
What steps will reproduce the problem?
1. Do a POST to a URL with multiple copies of a parameter with the same name,
but different values. Example:
usernames=itchy
usernames=scratchy
2. Observe i…