|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #72607 Wrong content-encoding on response
Submitted: 2016-07-17 12:23 UTC Modified: -
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: masood dot 63 at gmail dot com Assigned:
Status: Open Package: SOAP related
PHP Version: 5.6Git-2016-07-17 (snap) OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
16 - 11 = ?
Subscribe to this entry?

 [2016-07-17 12:23 UTC] masood dot 63 at gmail dot com
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.


Add a Patch

Pull Requests

Add a Pull Request

PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Tue Nov 12 10:01:35 2019 UTC