shribe

FWIW, I just hit this problem with only a few KB, (one terminal screen full or so, no loops, just individual logging statements), and it cost me a day chasing...

On Mar 2, 2016, at 1:49 PM, Benoit Chesneau [email protected] wrote: > @shribe for now it is expected to send the body immediately and then automatically answering. Your usage makes...

Here's an example URL that had a problem: http://us.rd.yahoo.com/finance/external/investopedia/rss/SIG=12kf3hrkl/*http://www.investopedia.com/news/microsoft-tests-chat-transcription-xbox-one-msft/?partner=YahooSA The fundamental issue is that it is not possible to know whether a URL passed into hackney is already encoded. You...

I don't believe I am misreading it. You can have a URL where hackney will literally encode some "%" characters but not others. That's just flat-out wrong. (And, in my...

I should also have said that, as far as I am concerned, an option to not attempt to encode the URI solves it.

I understand that it is the way it is right now, and that you have to be careful about changing the behavior.

ok, done -- Scott Ribe [email protected] https://www.linkedin.com/in/scottribe/ > On Aug 12, 2019, at 4:54 AM, gnzlbg wrote: > > You probably need to add the new modules to: https://github.com/fitzgen/mach/blob/master/mach-test/test/main.rs >...

if you're wondering why I never followed up: after getting this working, I discovered that the mach high-precision clock functions are SO SLOW they are worthless in any context where...

A note: I started over in a new session this morning, set access key, token, endpoint: didn't work--it was again trying to access `https://.s3.amazon.aws.com/path`. So it turns out that in...

I find that if I set the region and endpoint, it works--url_style does not matter. It seems that setting region and endpoint takes precedence over url_style when figuring out how...