Ideas on capturing SSL Data

[Heinz Ketchup]

There aren't too many solutions, but... if anyone might have an idea, I'd love to hear it.

We are connecting to a website using SSL. We submit data through their website (user data), and wait for a reponse on their side (confirmation / rejection). Our problem now is that their website / programmers aren't willing to compromise on a flaw we detected, this why we are interested in capturing the user data being sent and the response they provide. This is for C-SOX purposes. If you don't know about C-SOX, it's b/c of the Enron Scandle, and the Accounting nightmare they caused.

So, one posed solution is to create our own webserver, mirror they're page, and have our webserver communicate to their webserver, while we capture the data being sent from us to them, and receiving it from them to us, passing on the data from our webserver to the users screen (middle man service). It should be seamless, this way we get both in/out traffic data.

Downside to this is that the website we do interaction with constantly changes their data fields without warning or notice. So anything we mirror could have a sudden change that might crap things out.

This is only 1 suggestion.

If there are any out there, plz feel free to help. This seems like a bad work around, but we are running short on ideas.

The data is submitted from a button on their screen, and the response is a pop up form box from their website indicating data confirmation / rejection.

Our purpose is to track changes for same time frames. The user submits data for date "X", then needs to make another change for same date "X", we want to track that change, as the website only shows the current value.

Again, this is for C-SOX purposes and has a financial impact on our company.

Thanks,
Heinz