Re: More issues with the IRP tests

Please have both transitions in there:

  <transition event="HTTP.POST" conf:messageBodyEquals="this+is+some+content" conf:targetpass=""/>
  <transition event="HTTP.POST" conf:messageBodyEquals=“this%20is%20some%20content" conf:targetpass=""/>

The space -> ‘+’ is defined per RFC, but the space -> ‘%20’ is commonly seen with urlencoding as well.
  Stefan

On Jun 27, 2014, at 22:24, Jim Barnett <[email protected]> wrote:

> Fixed, I think.
> 
> - Jim
> 
> -----Original Message-----
> From: Stefan Radomski [mailto:[email protected]] 
> Sent: Friday, June 27, 2014 4:14 PM
> To: [email protected] ([email protected])
> Subject: More issues with the IRP tests
> 
> - test446.txt[1] is a 404
> You can use [2] to check for 404s (though with 1s delay between links)
> 
> - test520 has the content in <content> already urlencoded, which will lead to an urlencoded urlencoding:
> 'this%20is%20some%20content' -> 'this%2520is%2520some%2520content' (% is escaped as %25)
> 
> What is needed is:
>  <content>this is some content</content> ...
>  <transition event="HTTP.POST" cond="_event.raw.search(/this%20is%20some%20content/) !== -1" target="pass"/>
> 
> And I'd like to add
> 
>  <transition event="HTTP.POST" cond="_event.raw.search(/this+is+some+content/) !== -1" target="pass"/>
> 
> as '+' is a valid escaping for ' ' as well.
> 
> If this is corrected, we pass all tests but 579 with the history transitions and I will submit yet another updated IRP report.
> 
> Best regards
>  Stefan
> 
> [1] http://www.w3.org/Voice/2013/scxml-irp/446/test446.txt
> [2] http://validator.w3.org/checklink
> 
>