problem receiving XML via HTTP Post in webMethods 8.2.2

, ,
21

Are you not satisfied with Coherence default clustering?..Do you have terracotta licensing?

Just curious:

HTH,
RMG

22

coherence is not supported on VM I believe, one of the reasons SAG support recommended Terracotta; yes we do have license for Terracotta for IS clustering.

Regards
Deepan

23

Got u…Thanks for the update:

24

-update for the issue with http requests–
customer was sending XML as URL encoded which was not recognised by 82 IS, customer agreed to change in their side to remove the url encoding and test went ok.
other way we could resolve this is write a custom content handling service, extract the xml string from contentStream then decode the url encoding to get the xml string.

Strange, that same request was accepted in 65 but not in 82, may be we missed some server settings or parameters??

25

Nope…but they shouldn’t be changing simple/standard stuff:

26

Nope…but they shouldn’t be changing simple/standard stuff:

What URL encoding?

27

I have no chance to look at how customer is sending data. however this is my observation

  1. The xml sent by customer is URL encoded - %3C for <, %3E for < etc…
  2. This request when sent to 65 server it is recognised and IS places “node” in the service pipeline
  3. When sent to 82 server, this is not recognised and we get “contentStream” in pipeline; when converted to string, we get the URL encoded XML.

I wish nothing changed in the standard stuff; still wondering any settings or other parameters causing this.

28

Make sure they set the content-type=text/xml while sending HTTP post string data…If not ask for more details on their methods:

As far I know no standard settings changed the receiving style: