developer.jelix.org is not used any more and exists only for history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Opened 11 years ago

Closed 11 years ago

#1170 closed bug (fixed)

jResponse: should not force HTTP/1.1

Reported by: Julien Owned by: Julien
Priority: high Milestone: Jelix 1.2RC1
Component: jelix:core response Version: trunk
Severity: major Keywords:
Cc: Blocked By:
Blocking: Documentation needed: no
Hosting Provider: Php version:

Description

Took me hours to figure out why jWSDL wouldn't work from a simple soap client script on prod server, as it worked on my dev platform.

The reason is that when using HTTP/1.1, the prod server would send the content as a chunked Transfer Encoding, which is not supported by php SoapClient?.

The solution is to look at the HTTP version used for the request and to reply with the same version (see patch)

Attachments (1)

jResponse-HTTP-protocol.patch (1.8 KB) - added by Julien 11 years ago.

Download all attachments as: .zip

Change History (5)

Changed 11 years ago by Julien

comment:1 Changed 11 years ago by Julien

  • review set to review?
  • Status changed from new to assigned

comment:2 Changed 11 years ago by laurentj

  • review changed from review? to review+

comment:3 Changed 11 years ago by laurentj

please, in the commit user name, use "Julien Issler" or "julieni", since there is already an other julien. (change your ~/.hgrc for example)

comment:4 Changed 11 years ago by Julien

  • Resolution set to fixed
  • Status changed from assigned to closed

ok will change that

too late for this one... sorry

https://bitbucket.org/jelix/jelix-trunk/changeset/415da4d0870d

Note: See TracTickets for help on using tickets.