I'm using the Customer Information Manager secure popup functionality and, for some reason, I, my client, and our customers are intermittently getting Page Not Found messages when opening the popup in Chrome. The request is actually getting a 404 header response, and going directly to https://secure.authorize.net/profile/editPayment returns the same message.
After a few minutes, the issue resolves itself and both locations return the correct page (the direct link returns a Missing or invalid token error, but it is the correct page). The people receiving this error are spread out across the U.S. on multiple different ISPs, so it's not likely a network connectivity issue unless it's on AuthorizeNet's end.
Has anyone else been getting or had been getting this error and are there any solutions? Thanks!
12-13-2011 01:06 PM
Check out this post from 5 months ago... Haven't looked into it yet. Just found it.
Obviously Authorize doesn't read their forum...
12-20-2011 09:41 AM
We're going to place some additional monitoring on these services and see if we can find out what's causing these errors for you. I'll let you know if we are able to help resolve them for you.
Just to be clear though, the errors mentioned in the thread linked by st are completely unrelated. We apparently failed to respond to that thread when it was posted, but the cause of those errors are simply invalid URLs. It happens when someone mistakenly puts a trailing slash at the end of the hosted form URL such as https://test.authorize.net/profile/manage/ instead of https://test.authorize.net/profile/manage. This causes a problem with the relative URLs. The correct url for the stylesheet for example is https://test.authorize.net/profile/styles/profileCommon.css. Notice that it lacks the extra "/manage" subdirectory shown in that other thread.
12-20-2011 12:55 PM
Thanks. I do plan on adding some logging on our end to log the URL used each time it is used to see if there are any that ever go out malformed.
12-20-2011 01:57 PM
I don't know if it's entirely that, though - I've clicked the link back at the start of the thread and had it work some of the time and fail at least once. One would think it would either work all of the time or none of the time if you're correct about that being the problem.
12-20-2011 08:10 PM