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

[Gustav Ulander]

Yepp thats the plan. 
We are looking at london LD 5 as discussed earlier. We will probably start that project in Q2 or Q3. 
Otherwise we are loosly discussing what can be done for our Singapore office but that's there we don't have any real plans.

//gustav

-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Phil Shafer
Sent: den 3 februari 2016 20:50
To: Ola Thoresen <ola at nytt.no>
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] SLAX/Curl is html-entity-encoding content

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

    <contents> {
       uexpr $query;
    }

Deep knowledge is here:

https://www.w3.org/TR/xslt#disable-output-escaping

Thanks,
 Phil
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp