The backtrace is at the bottom of my first email. This is affecting others
so let's leave it on the list for now.

On Fri, Aug 13, 2021, 11:41 PM Thomas Baumgart via KMyMoney-devel <
kmymoney-devel@kde.org> wrote:

> On Samstag, 14. August 2021 01:15:57 CEST Jack via KMyMoney-devel wrote:
>
> > Well, searching for that error message is not encouraging. Incapsula
> > seems to be a web security tool added in front of the website.  That may
> > be why it needs the user-agent header.  Right now, I can only think of
> > two things to try.  First, try going the the URL you are using in a
> > browser.  It's not likely to help, but it might show something useful.
> > The other thing is to catch the entire process in GnuCash using
> > WireShark.  Unfortunately, I suspect the only thing it will do is
> > confirm the need for the user agent.
> >
> > One other possible line of attack - I think I see where in the code the
> > HTTP user agent could be added.  It should be easy enough for testing,
> > but would have to be wrapped in some sort of conditional (based on the
> > institution) for actual use.  We could work on that in private email,
> > and return to the list if it's succesful.
>
> If you take this off-list is fine but would you keep in in CC please? Thx.
>
> BTW: the quickest way to bring you back up to speed would be to solve the
> crash situation since the AqBanking integration has proven to work.
> If you could provide me with a backtrace of the crash I could start
> analyzing it.
>
> I use KBanking/AqBanking on a daily basis here, but with the HBCI and not
> the OFX backend. Did not experience any crashes for a very long time. Since
> it is working with GnuCash I expect the crash to happen in/be caused by
> KMyMoney
> code (which we can fix).
>
> Thomas
>
>
> --
>
> Regards
>
> Thomas Baumgart
>
> https://www.signal.org/       Signal, the better WhatsApp
> -------------------------------------------------------------
> If Windows is the answer I want my problem back!
> -------------------------------------------------------------
>

Reply via email to