| Age | Commit message (Collapse) | Author |
|---|
|
|
|
WIP
|
|
The current logic in `js_to_json` tries to rewrite octal/hex numbers to
decimal. However, when the logic actually happens the `"` or `'` have
already been trimmed off. This causes what were originally strings, that
happen to look like octal/hex numbers, to get rewritten to decimal and
returned as a number rather than a string.
In practive something like:
```js
{
"0x40": "foo",
"040": "bar",
}
```
would get rewritten as:
```json
{
64: "foo",
32: "bar
}
```
This is problematic since this isn't valid JSON as you cannot have
non-string keys.
|
|
|
|
|
|
+ Add support for UTF-8 in cookie files
* Skip malformed cookie file entries instead of crashing (invalid entry len, invalid expires at)
|
|
|
|
According to [1] TABs must be used as separators between fields.
Files produces by some tools with spaces as separators are considered
malformed.
1. https://curl.haxx.se/docs/http-cookies.html
This reverts commit cff99c91d150df2a4e21962a3ca8d4ae94533b8c.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Despite visual similarity "þ" is unrelated to "p".
It is normally transliterated as "th":
$ echo þ-Þ | iconv -t ASCII//TRANSLIT
th-TH
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(closes #18961)
|
|
|
|
|
|
expressions (closes #18600, closes #18805)
|
|
|
|
|
|
|
|
|
|
it can be read if it matches expected_status (resolves #17195, closes #17846, resolves #17447)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<location> can have relative URIs, not just absolute.
|
