regardless of content negotiation via Accept-Encoding: in the request.
Well, it was. This got fixed yesterday so it no longer applies. But
continuing with the issue...
Since the content negotiation was not working properly, I believe that using
Fetch::HTTPTiny, Fetch::CurlCommand, or Fetch::Wget plugins would break
when trying to pass the text/html content as they would not be able to decode
the content. By changing the Fetch plugin to Fetch::LWP, the response would
be decoded properly.
In a particular case, I had a server that was always returning a response with
Content-Encoding: gzip:regardless of content negotiation via
Accept-Encoding:in the request.Well, it was. This got fixed yesterday so it no longer applies. But continuing with the issue...
Since the content negotiation was not working properly, I believe that using
Fetch::HTTPTiny,Fetch::CurlCommand, orFetch::Wgetplugins would break when trying to pass thetext/htmlcontent as they would not be able to decode the content. By changing the Fetch plugin toFetch::LWP, the response would be decoded properly.