DataPower

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)

Clear this up for us:

>> Is there a way to catch this error and avoid to have an error rule triggered?

and then:

>> So it will be nice if dp:decode can be catched in case of failure

In my mind, the error rule is DataPower giving you the opportunity to handle the error in case of decode failure.   In the error rule, you'll likely want to return some kind of error to the client, maybe an HTTP 400 if you want to be explicit about a bad request, or an HTTP 404 if you want to indicate the resource at the URL cannot be found, prompting the client to check the manner in which their URL is constructed.

Do you want DataPower not to fire off the error rule if there is an error?   You can always use an on-error action with it set to continue.  Not sure what you plan to do after that, but at least the error rule won't be fired.

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)

hello

Thanks for response :)

In my ideal world, i want to decode and url and even if an error in generated, i don't want datapower triggered an error rule because my treatment has to be finished.

in other words, I'm looking to know if there is some kind of try/catch for this kind of command :)

Clear this up for us:

>> Is there a way to catch this error and avoid to have an error rule triggered?

and then:

>> So it will be nice if dp:decode can be catched in case of failure

In my mind, the error rule is DataPower giving you the opportunity to handle the error in case of decode failure.   In the error rule, you'll likely want to return some kind of error to the client, maybe an HTTP 400 if you want to be explicit about a bad request, or an HTTP 404 if you want to indicate the resource at the URL cannot be found, prompting the client to check the manner in which their URL is constructed.

Do you want DataPower not to fire off the error rule if there is an error?   You can always use an on-error action with it set to continue.  Not sure what you plan to do after that, but at least the error rule won't be fired.

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)

Hi D@viiid, 
First, the 2nd argument to the dp:decode is a string, so your statement should have url in single quotes as a string literal

<xsl:variable name="decodedUrl" select="dp:decode('test%11','url')"/>

After this is done, I logged to the console the string-length($decodedUrl) and received an answer of 5, so the decode did work. Now a %11 in ascii is actually a DC1 (Device Control 1 - x11), but my question is why are you having any invalid ascii character %11 in the url string to be decoded??? By the way, don't try to write that variable to the console as a x11 causes a failure of the logging subsystem and thus the xslt will get a runtime error. If I change that value to have a valid ascii character I would expect to see in a url, say %2B (a + character), then the decoded string is test+ as expected.

Bottom line, dp:decode, assuming the 2nd argument is properly specified, is translating %xx to the associated ascii xx character and is not failing, but the character it is translating may cause the logging system heartburn if you try to do an xsl:message and write its value to the default logs.  What is your use case that %11 is trying to handle?

Regards,

Steve

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)

Hello Steve

sorry for confusion : yes my example is not relevant.

What i received is 'test%2525´ and in this case I had to double escape (first to pass from %2525 to %25, second to pass from %25 to %)

but since couple of Week, I also receive %25. (Or other caracters escape only on Time)

In my code, i used a couple of dp:decode and it works fine for %2525 but not for %25.

Is it more clear ?

maybe I can use gw function call from my stylesheet to decode string and use try/catch to avoid error and continue process in the stylesheet 

what do you mean ?

:)

------------------------------
D@viiid

Original Message:
Sent: Tue February 27, 2024 04:24 PM
From: Steve Linn
Subject: dp:decode('test%11',url)

Hi D@viiid, 
First, the 2nd argument to the dp:decode is a string, so your statement should have url in single quotes as a string literal

<xsl:variable name="decodedUrl" select="dp:decode('test%11','url')"/>

After this is done, I logged to the console the string-length($decodedUrl) and received an answer of 5, so the decode did work. Now a %11 in ascii is actually a DC1 (Device Control 1 - x11), but my question is why are you having any invalid ascii character %11 in the url string to be decoded??? By the way, don't try to write that variable to the console as a x11 causes a failure of the logging subsystem and thus the xslt will get a runtime error. If I change that value to have a valid ascii character I would expect to see in a url, say %2B (a + character), then the decoded string is test+ as expected.

Bottom line, dp:decode, assuming the 2nd argument is properly specified, is translating %xx to the associated ascii xx character and is not failing, but the character it is translating may cause the logging system heartburn if you try to do an xsl:message and write its value to the default logs.  What is your use case that %11 is trying to handle?

Regards,

Steve

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM

Original Message:
Sent: Tue February 27, 2024 05:51 AM
From: D@viiid
Subject: dp:decode('test%11',url)

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)

------------------------------
D@viiid
------------------------------

Hello Steve

sorry for confusion : yes my example is not relevant.

What i received is 'test%2525´ and in this case I had to double escape (first to pass from %2525 to %25, second to pass from %25 to %)

but since couple of Week, I also receive %25. (Or other caracters escape only on Time)

In my code, i used a couple of dp:decode and it works fine for %2525 but not for %25.

Is it more clear ?

maybe I can use gw function call from my stylesheet to decode string and use try/catch to avoid error and continue process in the stylesheet 

what do you mean ?

:)

Hi D@viiid, 
First, the 2nd argument to the dp:decode is a string, so your statement should have url in single quotes as a string literal

<xsl:variable name="decodedUrl" select="dp:decode('test%11','url')"/>

After this is done, I logged to the console the string-length($decodedUrl) and received an answer of 5, so the decode did work. Now a %11 in ascii is actually a DC1 (Device Control 1 - x11), but my question is why are you having any invalid ascii character %11 in the url string to be decoded??? By the way, don't try to write that variable to the console as a x11 causes a failure of the logging subsystem and thus the xslt will get a runtime error. If I change that value to have a valid ascii character I would expect to see in a url, say %2B (a + character), then the decoded string is test+ as expected.

Bottom line, dp:decode, assuming the 2nd argument is properly specified, is translating %xx to the associated ascii xx character and is not failing, but the character it is translating may cause the logging system heartburn if you try to do an xsl:message and write its value to the default logs.  What is your use case that %11 is trying to handle?

Regards,

Steve

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)

Hi D@viiid,

> What i received is 'test%2525´ and in this case I had to double escape (first to pass from %2525 to %25, second to pass from %25 to %)
> but since couple of Week, I also receive %25. (Or other caracters escape only on Time)
>
first, DataPower implements standards, and if that would be my service, I would just error out on double encoded input.
This would force clients breaking standards to fix their application.
That is for an ideal world.

Before URL decoding to handle double encoded as well as normal encoded:
Use "contains($url,'%2525')" to decide whether you want double decode or not:
https://www.w3.org/TR/1999/REC-xpath-19991116/#function-contains

Hello Steve

sorry for confusion : yes my example is not relevant.

What i received is 'test%2525´ and in this case I had to double escape (first to pass from %2525 to %25, second to pass from %25 to %)

but since couple of Week, I also receive %25. (Or other caracters escape only on Time)

In my code, i used a couple of dp:decode and it works fine for %2525 but not for %25.

Is it more clear ?

maybe I can use gw function call from my stylesheet to decode string and use try/catch to avoid error and continue process in the stylesheet 

what do you mean ?

:)

Hi D@viiid, 
First, the 2nd argument to the dp:decode is a string, so your statement should have url in single quotes as a string literal

<xsl:variable name="decodedUrl" select="dp:decode('test%11','url')"/>

After this is done, I logged to the console the string-length($decodedUrl) and received an answer of 5, so the decode did work. Now a %11 in ascii is actually a DC1 (Device Control 1 - x11), but my question is why are you having any invalid ascii character %11 in the url string to be decoded??? By the way, don't try to write that variable to the console as a x11 causes a failure of the logging subsystem and thus the xslt will get a runtime error. If I change that value to have a valid ascii character I would expect to see in a url, say %2B (a + character), then the decoded string is test+ as expected.

Bottom line, dp:decode, assuming the 2nd argument is properly specified, is translating %xx to the associated ascii xx character and is not failing, but the character it is translating may cause the logging system heartburn if you try to do an xsl:message and write its value to the default logs.  What is your use case that %11 is trying to handle?

Regards,

Steve

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)

Hello Steve

sorry for confusion : yes my example is not relevant.

What i received is 'test%2525´ and in this case I had to double escape (first to pass from %2525 to %25, second to pass from %25 to %)

but since couple of Week, I also receive %25. (Or other caracters escape only on Time)

In my code, i used a couple of dp:decode and it works fine for %2525 but not for %25.

Is it more clear ?

maybe I can use gw function call from my stylesheet to decode string and use try/catch to avoid error and continue process in the stylesheet 

what do you mean ?

:)

Hi D@viiid, 
First, the 2nd argument to the dp:decode is a string, so your statement should have url in single quotes as a string literal

<xsl:variable name="decodedUrl" select="dp:decode('test%11','url')"/>

After this is done, I logged to the console the string-length($decodedUrl) and received an answer of 5, so the decode did work. Now a %11 in ascii is actually a DC1 (Device Control 1 - x11), but my question is why are you having any invalid ascii character %11 in the url string to be decoded??? By the way, don't try to write that variable to the console as a x11 causes a failure of the logging subsystem and thus the xslt will get a runtime error. If I change that value to have a valid ascii character I would expect to see in a url, say %2B (a + character), then the decoded string is test+ as expected.

Bottom line, dp:decode, assuming the 2nd argument is properly specified, is translating %xx to the associated ascii xx character and is not failing, but the character it is translating may cause the logging system heartburn if you try to do an xsl:message and write its value to the default logs.  What is your use case that %11 is trying to handle?

Regards,

Steve

Hello

Just a quick question about this command : dp:decode('test%11',url)

This command thrown an error because the % is not escaped  (%25 expected)

Is there a way to catch this error and avoid to have an error rule triggered ?

Some time client send double escapement (%25C3%25A9 first decode--> %C3A9 seconde decode --> é) but sometime, client just send %c3a9.

So it will be nice if dp:decode can be catched in case of failure

Any workaround ? thanks :)