[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=377368

--- Comment #8 from geo...@wildturkeyranch.net ---
On 08/08/17 00:24, Thomas Baumgart wrote:
> George, you forgot
>
> 3) get the developers for the bank's backend system to read and understand the
> RFC and fix the problem (hey, after all they introduced it)
Yeah, well I long ago realized that my tail was NOT going to wag the 
dog. So the only chance at resolution was to grab the bull by the horn, 
so to speak.
>
> though your solution to 'stop using the card' on a wide scale may have some
> impact  (I have dreaming mode on while I write this) and would be my choice as
> well.
>
> As to 1) why should there be an option to control the order if that is not
> required by the standard and 2) only if said bank pays me so that I can retire
> immediately and take care of KMyMoney fulltime.
Sorry, Quicken already paid THEM.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[Thomas Baumgart]

https://bugs.kde.org/show_bug.cgi?id=377368

Thomas Baumgart  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Thomas Baumgart  ---
George, you forgot

3) get the developers for the bank's backend system to read and understand the
RFC and fix the problem (hey, after all they introduced it)

though your solution to 'stop using the card' on a wide scale may have some
impact  (I have dreaming mode on while I write this) and would be my choice as
well.

As to 1) why should there be an option to control the order if that is not
required by the standard and 2) only if said bank pays me so that I can retire
immediately and take care of KMyMoney fulltime.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=377368

--- Comment #6 from geo...@wildturkeyranch.net ---
Looks like two choices to me:

1) Get the folks who's code your using to give you a fix, possibly an 
addition option to order the header, or

2) Grab/purloin/etc. said code, fix the issue and make that part of 
Kmymoney.

To me, the problem is the solution is dead in the water, and, for me, 
has caused me to stop using the card.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[Jack]

https://bugs.kde.org/show_bug.cgi?id=377368

--- Comment #5 from Jack  ---
George - do you have a suggestion as to who needs to act?  The comments above
indicate there is absolutely nothing within the KMyMoney code which can help.

Thomas - is there any point in trying to bring in the KIO developers, at least
to ask if there is anything they can do?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=377368

--- Comment #4 from geo...@wildturkeyranch.net ---
I too have this problem. 
The comments above seem to indicate that it is, in fact, a problem (even if it
is not a bug as suggested above).

What does it take to get some action here?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=377368

geo...@wildturkeyranch.net changed:

   What|Removed |Added

 CC||geo...@wildturkeyranch.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=377368

--- Comment #3 from wuzhuoq...@hotmail.com ---
Ok, tried a few things and finally settled with one dirty workaround for
myself. Basically changed the code to call a custom python 2 script (which use
httplib to fine control the header order) to send the ofx request first, and if
not succeeded (script return non 0 code) then fallback to original code path.

Obvious this is not good for PR. Just in case anyone is interested
https://github.com/Zhuoqing/kmymoney_discover_workaround/commit/3f7acce5fcc51cea1e9bac11e3edae8a4d8231d9

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=377368

--- Comment #2 from wuzhuoq...@hotmail.com ---
Thanks. Indeed, seems there is no easy way to work around this unless change
the kio http slave code
https://cgit.kde.org/kio.git/tree/src/ioslaves/http/http.cpp

I think I will just live with it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[Thomas Baumgart]

https://bugs.kde.org/show_bug.cgi?id=377368

--- Comment #1 from Thomas Baumgart  ---
The actual request is created in "bool KOfxDirectConnectDlg::init()" which can
be found in
https://github.com/KDE/kmymoney/blob/4.8/kmymoney/plugins/ofximport/dialogs/kofxdirectconnectdlg.cpp
. The problem is that the metadata handling is completely handled within
KIO::TransferJob which we simply utilize. The metadata is transported using a
QMap container, so changing/controlling the order
of the entries is not that easy.

It looks like the order of HTTP Headers doesn't matter for headers with
different names. If there are multiple headers with the same name, however, the
order is important. More details can be found in the respective RFC at
http://tools.ietf.org/html/rfc2616#section-4.2. 

If the bank's server still requires a certain order it is simply not compliant
with the RFC and thus broken (just like so many other bank systems).

-- 
You are receiving this mail because:
You are watching all bug changes.