Avatar for Username

Cari Bantuan

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Pelajari Lebih Lanjut

Utas ini telah diarsipkan. Silakan membuat pertanyaan baru jika Anda membutuhkan bantuan.

USBank returns a zero length file in response to a download request

  • 2 balas
  • 3 memiliki masalah ini
  • 8 kunjungan
  • Balasan terakhir oleh DougMcNutt

DougMcNutt
DougMcNutt
more options

Firefox 28.0 on ubuntu linux 1310

A recent change in USBank's website has resulted in zero length transaction files being downloaded. Live HTTP headers seems to show transmission of a zero length file. Firefox creates the file export.csv in /home/doug/Downloads but leaves it empty without complaint. A repeat creates export(2).csv which UNIX users would frown upon because of the parentheses but it's not clear whether that's done by Firefox or USBank. Asking for one of their Quicken formats also results in zero length.

Firefox sometimes seems to ignore data in other USBank's fill out forms. Adding a biller to its CheckFree list won't work either and I think that might be a result of Java (Not JavaScript) code. I worry about iced tea which I know little about. USBank does offer, until mid May, access to their old code which works fine.

Looking at the headers there are lots of references to Google and there are huge random number cookies being sent around.

USBank's response is that we don't support Firefox because it's open source. Other banking suggestions are welcome.

Firefox 28.0 on ubuntu linux 1310 A recent change in USBank's website has resulted in zero length transaction files being downloaded. Live HTTP headers seems to show transmission of a zero length file. Firefox creates the file export.csv in /home/doug/Downloads but leaves it empty without complaint. A repeat creates export(2).csv which UNIX users would frown upon because of the parentheses but it's not clear whether that's done by Firefox or USBank. Asking for one of their Quicken formats also results in zero length. Firefox sometimes seems to ignore data in other USBank's fill out forms. Adding a biller to its CheckFree list won't work either and I think that might be a result of Java (Not JavaScript) code. I worry about iced tea which I know little about. USBank does offer, until mid May, access to their old code which works fine. Looking at the headers there are lots of references to Google and there are huge random number cookies being sent around. USBank's response is that we don't support Firefox because it's open source. Other banking suggestions are welcome.

Solusi terpilih

There was a hack for this a while back, please see question/953639.

Actually, since its the downloads that are not working, it is possible to try to log the HTTP headers to see where checksum becomes different. Though a secure network would check this?

Baca jawaban ini dalam konteks 👍 1

Semua Balasan (2)

guigs
guigs
more options

Solusi Terpilih

There was a hack for this a while back, please see question/953639.

Actually, since its the downloads that are not working, it is possible to try to log the HTTP headers to see where checksum becomes different. Though a secure network would check this?

Diperbarui oleh guigs pada

DougMcNutt
DougMcNutt Pemilik pertanyaan
more options

953639 is well known by me. I actally contributed to it. USBank repaired their problem. which was not allowing any connection at all without using the "most recent" version of Firefox which to them was 17.

"Resetting" Firefox using the instructions has apparently fixed the problem but it's also possible that US bank has fixed its software since I had the problem.

There are no firewalls involved.

I haven't figured out exactly how to persuade Firefox's preferences to troubleshoot problems. Is it a recompile with a debug flag set?

Next step is to reinstall support for Java beans, Live HTTP headers, and some scripting. I'll do them one at a time and report if I get more zero length files.

Many thanks to guigs2.