Dezső BICZÓ

Hi! I'm using your module in my web crawler, called [Web page Content Extractor (wce)](https://www.npmjs.com/package/wce), and I've recently discovered that the read-art returns with "Error: 400 Bad Request" for these...

Thanks for the fast reaction! I was suspicious too, that this should a req-fast issue. I can confirm, that the content extraction works fine on these links now with read-art.

I see that this looks like a valid workaround for the problem but is it the right way to get it solved? Aren't we trying to abuse Composer? Can we...

I see conversation happens about the same topic in several places :) Let me reference my comment from an other one: https://github.com/composer/composer/pull/9792#issuecomment-807983199 > to create a PHAR to be able...

Has anything related happened outside of this thread in the past year?

Based on the progress and activity on the upstream repo, it seems to me it is time to (fork and) replace the Mega provider. Although, I'm not sure if anybody...

With the current Xdebug configuration I can see notices like this: `NOTICE: PHP message: Xdebug: [Log Files] File '/proc/self/fd/2' could not be opened.` Could be related to https://github.com/docker-library/php/issues/358#issuecomment-271033464

So even client plugins can not throw an exception when settle() is in use with Guzzle6 adapter because you get the same unexpected behaviour. ```php

@sagikazarmark As maintainer of this library and Guzzle could you share your 2 cents please?

@sagikazarmark Thanks for looking into this. > I suspect that somewhere there is a plain wait call which is indeed not an issue if the unwrapped value is a promise...