Thank you for the assistance.
Are you using https? are you using the absolute path on the response.redirect?
Yes to https, and yes the response.redirect was going to an absolute path beginning with https://www.. full URL to specific page.
Do a javascript redirect instead on a code behind Response.redirect.
I am still trying to figure out how to do this in my specific configuration. Let me elaborate and then hopefully you can help me because at the moment I am stuck.
And you have the EnableViewStateMac set to false?
I have not modified this setting, so it's current state is probably true if that is the default setting
The reason it relay response is like doing a webrequest on your page and using that info to display it on test.authorize.net website.
So far I have done the following:
1) comment out the response.redirect. After this, there is no longer a 404 error.
If I place a static URL a href =xxx on the aspx page, then it will display on the authorize.net server as you stated, no error.
My current problem is that I need to build the URL dynamically, and then display it for the user to click. Ideally I would like to automatically redirect the user, but at this point I'll take what I can get because this is the last step in my implementation.
What I have tried so far is to create a variable in my code-behind that stores the full URL.
On the aspx page I tried to display at as follows: a href="<%= redirectURL %>">some text here<end a tag>
WHen I try to do the above, I get a timeout error on the page (as opposed to the 404).
Even if I do a javascript redirect, I would still like to append a dynamic query string to it ?key=val, before redirecting back to my biz app.
Just for full disclosure, on the Relay Response URL I do have business logic that interacts with the biz app server. This all works great. The final step is simply to bring the user back to the biz app web server via a redirect (or link if need be) with the dynamic URL I build on the code behind page.
I admit my asp is very rusty, so some of this is probably easy to someone who has been working with asp.net more frequently than me. Thanks in advance for any assistance you can provide.