Bug #72607 [Opn->Wfx]: Wrong content-encoding on response

Edit report at https://bugs.php.net/bug.php?id=72607&edit=1 ID: 72607 Updated by: cmb@php.net Reported by: masood dot 63 at gmail dot com Summary: Wrong content-encoding on response -Status: Open +Status: Wont fix Type: Bug Package: SOAP related PHP Version: 5.6Git-2016-07-17 (snap) -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: I don't think that ignoring a Content-Type header makes sense, because if the payload is actually compressed, it would let the XML parser fail in an arbitrary way. > this is a mistake on developing server-side web service Indeed, and it shouldn't be hard to fix that. Previous Comments: ------------------------------------------------------------------------ [2016-07-17 12:23:14] masood dot 63 at gmail dot com Description: ------------ in SoapCleint when response has wrong content-encoding value, a SoapFault Exception occurring with "Unknown Content-Encoding" message. its better to developer can ignore encoding on response. for example Content-Encoding was set as "text/xml; charset=1256" instead of setting by "gzip" or etc. this is a mistake on developing server-side web service but cause to client side exception. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=72607&edit=1