Forum Moderators: phranque
This is my first post, and I'm as frustrated as could be.
First, a little background. I'm a webmaster for a small company that caters to courts, serveral of which accept payments of fines on-line via VeriSign's PayFlow Link service. These payment sites have been in place for over a year now, and everything was working great until VeriSign decided they needed to update their servers.
Aparently, their new system is a bit more particular than the old when it comes to the Status Code that it receives from the merchant's server on a Silent Post (Silent Post is how VeriSign sends data to the merchant's server after a completed transaction). I realized this after they switched their servers on 3/16/05 and all of my clients with the payment system in place contacted me to inform me that every attempted transaction is rejected with a "Communication Error with the Merchant's Server" message and consequently voided.
After speaking with VeriSign's customer support, I learned that the new system will ONLY accept a returned status of "200 OK". I checked my status code via web-sniffer.net, and it says the code is "200 OK", but in my Apache access log, all I see is "200". I wonder if web-sniffer.net automatically places the "OK" after any 200 response. VeriSign assured me that the only possible problem is with this status code.
My first question is, is the "200" I'm seeing on the requests in the access log the actual code that's being sent to the requesting browser? If not, is there a better way (other than web-sniffer.net) to get these codes exactly as they're sent?
And finally, is there a way to change how these codes are sent using only Apache 1.3.26 with a cgi script written in Perl? These are simple Apache installations, without mod_perl, PhP, etc. I do have some modules installed, mod_headers (which only changes the headers, not the status codes, from what I can tell), mod_rewrite, mod_env, and several other modules which I could list if necessary.
I'd really like to get this to work with the current configuration, just so I don't have to try to get Apache to compile on a SCO Unix system (I'm obviously not as tech savvy as many of you). Just thinking about that makes me consider going back to delivering pizzas. Ah, to be 16 again and void of any responsibilities. Anyway, any information any of you could offer would be extremely beneficial.
Thanks in advance and have a great day everyone!
[edited by: jdMorgan at 1:05 am (utc) on Mar. 18, 2005]
[edit reason] Obscured specifics, added formatting. [/edit]
I checked my status code via "example.com", and it says the code is "200 OK", but in my Apache access log, all I see is "200". I wonder if "example.com" automatically places the "OK" after any 200 response.
Both of these means that your server is in fact sending a status code "200 OK". Here's another tool that will show you the headers that your server send:
[webmasterworld.com...]
>> And finally, is there a way to change how these codes are sent using only Apache 1.3.26 with a cgi script written in Perl
Yes you can probably do that with a little effort. Try describing exactly what you want the script to do in the Perl/CGI forum [webmasterworld.com] and hear what the nice people say :)
I wrote "example.com" because we generally don't post URLs to tools and web sites on this board - it's in the TOS. The tool mentioned above is from WebmasterWorld so that one is okay
I understand your confusion, this is not totally easy to understand if you haven't looked at in in detail before.
The "HTTP/1.1" is no problem. It's the protocol (a "method" of some sort) that your browser uses to communicate with the server. This does not have anything to do with the code 200.
As long as the server header checker says "200" then you're OK - all the other lines has to do with other stuff than this.
