#29506

For anyone else who may run into this same issue, they have resolved it in a new release/patch. Essentially, this was only an issue for the .NET libraries.

#29507

@277opersuser wrote:

We are having an issue where the URL we are using is not the same as we provided, which is causing issues during renditioning. The URL contains reserved special characters within a query string value that have been URL encoded and it appears that PD4ML is decoding the URL when it attempts to retrieve the HTML. Is there a way to prevent the URL from being decoded? This seems like odd behavior considering it is best practice to use an encoded values in a URL when using reserved special characters.

Here is the encoded and decoded URL:
http://localhost/Somepage?key1=1B%2BTI8O2dDe%2BW1buq%2F0%2BAQ%3D%3D&key2=Testing

http://localhost/Somepage?key1=1B+TI8O2dDe+W1buq/0+AQ==&key2=Testing

Also, we are using version 385 for .NET 2.0.

#29840

@PD4ML wrote:

I’ve forwarded the question to our .NET team. I’ll let you know as soon as we have new info.

Much appreciated! However, we figured out it out. See below.

1. In the OnStart function of Windows Service Host class, add the following code:

Console.SetError(New System.IO.StreamWriter("[filename]")

2. Then in the OnStop function, add the following code:

Console.Error.Close()

I’m sure there are other ways to do this such as creating your own custom System.Diagnostics listener, but this way works too. One thing to note is that you will need to stop the service in order to see the logs that were written.

#29807

For anyone experiencing this same issue, I wanted let you know that a fix was implemented in the most recent release – 385. Also, I’ve attached a sample PDF to show what was happening.

[Author]

Posts