le%2Epy" which unencoded is this "\routingwizard_multiple.p
y" the script file to be executed.
The URL from above gets sent through C# code back to the web server, an auto login process for the application is used, and the URL gets decoded and re-coded during that process and added to a URL value of TARGET. The decoded URL is below:
That above URL is fine and looks good. The auto login process re-encodes the URL variables to this value, which is the problem.
It has interpreted the \r at the beginning of \routingwizard_multiple.py
to be a line feed. So the URL when it is decoded makes this which results in a time out because it is not executing the Python script call. The last URL is this:
Notice the line return now, and the script name outingwizard_multiple.py.
This breaks the application. Now it is time for the really good stuff. This works on a production system and does not have the URL hiccup. Code is a direct copy of that working code. Verified Encoding is the same in the same places config files, meta tags, IIS globalization. Versions of IIS are the same with the same service pack. Globalization settings are the same on the servers and the servers’ operating systems match to the correct service pack. IIS 6 on windows server 2003 service pack 2. Everything I can think of to check I have verified as I have been bogged down on this for over a week.
Does anyone have any suggestions, or directions that I could head down as I am totally stumped on this one. Putting the URL into encoder and decoders gets proper results. Why would it translate the \r in one instance, and not the other? Is there a way around this short of renaming files? I would like to find the underlying problem so I can make certain other script calls will not be miss-encoded.
Thanks, I know it is long and convoluted explanation, and I appreciate you die hard challengists that love a good one, cause here is a doozy.