[j-nsp] SLAX/Curl is html-entity-encoding content

2016-02-03 Thread Ola Thoresen
I am testing an op-script that is using curl to make a http-post to an external url. It seems to work OK, except that the content is "html-encoded", which causes errors when "the other end" don't expect it. Unfortunately I have no control over "the other end" so I can't easily make it

Re: [j-nsp] SLAX/Curl is html-entity-encoding content

2016-02-03 Thread Gustav Ulander
: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Phil Shafer Sent: den 3 februari 2016 20:50 To: Ola Thoresen <o...@nytt.no> Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] SLAX/Curl is html-entity-encoding content Ola Thoresen writes: >It seems to work O

Re: [j-nsp] SLAX/Curl is html-entity-encoding content

2016-02-03 Thread Phil Shafer
Ola Thoresen writes: >It seems to work OK, except that the content is "html-encoded", which >causes errors when "the other end" don't expect it. Use the "uexpr" statement to avoid escaping: http://juniper.github.io/libslax/slax-manual.html#uexpr { uexpr $query; } Deep