|
From: | Dmitry Gutov |
Subject: | Re: bug#23750: 25.0.95; bug in url-retrieve or json.el |
Date: | Fri, 2 Dec 2016 17:32:46 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Thunderbird/50.0 |
On 02.12.2016 17:29, Lars Ingebrigtsen wrote:
This is going to break many current callers. Most people aren't doing anything as weird as trying to transmit non-ASCII text via any of these headers (it's a very uncommon thing to do), but are just passing in normal Emacs strings (containing nothing by ASCII, as is proper).
Do you have some examples?
These will all fail if you do this, for no real gain.
That's debatable.
Sorry to keep harping on about this, but the current url-* interface is inadequate. We should leave it be and move on to create a new, well-defined url-fetching interface.
I'm sure a well-defined interface will need to have a required "encoding" step, or an argument somewhere, at least.
[Prev in Thread] | Current Thread | [Next in Thread] |