RESOLVED WORKSFORME27999
[Gtk] SNS online banking: confirming transaction only works in debug mode
https://bugs.webkit.org/show_bug.cgi?id=27999
Summary [Gtk] SNS online banking: confirming transaction only works in debug mode
Reinout van Schouwen
Reported 2009-08-04 14:51:23 PDT
The online banking application of the SNS Bank works mostly fine in Epiphany/Webkit. The only thing that doesn't work is the final confirmation of a money transfer order. When I click the 'Verzenden' button ('Send') nothing happens. I was trying to debug this with WEBKIT_DEBUG=Network and, to my surprise, confirming transactions works in debug mode! Back in normal mode, it fails. I have reproduced this a couple of times now. Here's a capture of the network traffic logged to the console when the Verzenden button is clicked (I've edited a serial number in one URL for security reasons): > POST /secure/Bankieren/scripts/verzendlijst/verzendlijst_checksum.asp HTTP/1.1 > Soup-Debug-Timestamp: 1249422138 > Soup-Debug: SoupSessionAsync 1 (0x1b40010), SoupMessage 149 (0x1b46bf0), SoupSocket 2 (0x1b4a240) > Host: www.snsbank.nl > Origin: https://www.snsbank.nl > User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; nl-nl) AppleWebKit/531.2+ (KHTML, like Gecko) Safari/531.2+ > Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 > Referer: https://www.snsbank.nl/secure/Bankieren/scripts/verzendlijst/verzendlijst_checksum.asp > Content-Type: application/x-www-form-urlencoded > Accept-Encoding: identity > Cookie: SNS_PERSIS=13256587161247846416870--1440x900; ASPSESSIONIDCQRCQBRQ=JMNOJLMDECCPJJGKBKNOBOHG; __utmz=229395038.1247846419.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=229395038.4006138691315477500.1247846419.1248026643.1248760636.3; MfPers=200907171800107413; MfTrack=200908042338297622 > > SequenceNo=11516012&SignMethod=digipas&DigipassSerial=88888888&signature1=691466&actie=VERZEND < HTTP/1.1 302 Object moved < Soup-Debug-Timestamp: 1249422138 < Soup-Debug: SoupMessage 149 (0x1b46bf0) < Date: Tue, 04 Aug 2009 21:42:12 GMT < Server: Microsoft-IIS/6.0 < X-Powered-By: ASP.NET < X-UA-Compatible: IE=EmulateIE7 < pragma: no-cache < cache-control: private < Location: verzendlijst.asp?SendOk=True&errmesg=1+opdracht%28en%29+verzonden < Content-Length: 190 < Content-Type: text/html < Expires: Mon, 03 Aug 2009 21:42:12 GMT < cache-control: no-cache > GET /secure/Bankieren/scripts/verzendlijst/verzendlijst.asp?SendOk=True&errmesg=1+opdracht%28en%29+verzonden HTTP/1.1 > Soup-Debug-Timestamp: 1249422138 > Soup-Debug: SoupSessionAsync 1 (0x1b40010), SoupMessage 149 (0x1b46bf0), SoupSocket 2 (0x1b4a240), restarted > Host: www.snsbank.nl > Origin: https://www.snsbank.nl > User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; nl-nl) AppleWebKit/531.2+ (KHTML, like Gecko) Safari/531.2+ > Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 > Referer: https://www.snsbank.nl/secure/Bankieren/scripts/verzendlijst/verzendlijst_checksum.asp > Accept-Encoding: identity > Cookie: SNS_PERSIS=13256587161247846416870--1440x900; ASPSESSIONIDCQRCQBRQ=JMNOJLMDECCPJJGKBKNOBOHG; __utmz=229395038.1247846419.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=229395038.4006138691315477500.1247846419.1248026643.1248760636.3; MfPers=200907171800107413; MfTrack=200908042338297622 < HTTP/1.1 200 OK < Soup-Debug-Timestamp: 1249422138 < Soup-Debug: SoupMessage 149 (0x1b46bf0) < Date: Tue, 04 Aug 2009 21:42:12 GMT < Server: Microsoft-IIS/6.0 < X-Powered-By: ASP.NET < X-UA-Compatible: IE=EmulateIE7 < pragma: no-cache < cache-control: private < Content-Length: 9872 < Content-Type: text/html < Expires: Mon, 03 Aug 2009 21:42:12 GMT < cache-control: no-cache
Attachments
Jan Alonzo
Comment 1 2009-08-05 03:41:27 PDT
CC'ing folks who may be able to help with this issue.
Dan Winship
Comment 2 2009-08-05 13:07:40 PDT
does WEBKIT_DEBUG=Network do anything besides attach a SoupLogger? I can't think of any reason why SoupLogger would change its behavior...
Reinout van Schouwen
Comment 3 2009-12-30 05:50:45 PST
This bug is obsolete as the website has changed and the online banking system now works as expected.
Note You need to log in before you can comment on or make changes to this bug.