Sigh, that's not it either: Sending: ------------------------------------- OFXHEADER:100 DATA:OFXSGML VERSION:102 SECURITY:NONE ENCODING:USASCII CHARSET:1252 COMPRESSION:NONE OLDFILEUID:NONE NEWFILEUID:20200318151247.000
<OFX><SIGNONMSGSRQV1><SONRQ><DTCLIENT>20200318151243<USERID>1801552<USERPASS>4376<LANG>ENG<FI><ORG>USAA<FID>24591</FI><APPID>QWIN<APPVER>2300</SONRQ></SIGNONMSGSRQV1><CREDITCARDMSGSRQV1><CCSTMTTRNRQ><TRNUID>20200318151247<CCSTMTRQ><CCACCTFROM><BANKID>24591<ACCTID>4270829065395045</CCACCTFROM><INCTRAN><DTSTART>20200309000000<DTEND>20200318000000<INCLUDE>Y</INCTRAN></CCSTMTRQ></CCSTMTTRNRQ></CREDITCARDMSGSRQV1></OFX> and a 400. Regards, John Ralls > On Mar 18, 2020, at 3:08 PM, Martin Preuss <[email protected]> wrote: > > Hi, > > hmm, so no linebreaks... > > Could either of you please try with the following lines commented out in > v1/n_toofx.c: > - 105: if (hasSubTags) > - 106: GWEN_Buffer_AppendString(buf, "\r\n"); > - 128: GWEN_Buffer_AppendString(buf, "\r\n"); > > Will be back in a few mins, have to watch an episode of "Bull" on my > wifes request... ;-) > > > Regards > Martin > > > Am 18.03.20 um 23:02 schrieb John Ralls: >> Remember, the working ofx from AQB5 is >> Sending: >> ------------------------------------- >> OFXHEADER:100 >> DATA:OFXSGML >> VERSION:102 >> SECURITY:NONE >> ENCODING:USASCII >> CHARSET:1252 >> COMPRESSION:NONE >> OLDFILEUID:NONE >> NEWFILEUID:20200315112517.000 >> >> <OFX><SIGNONMSGSRQV1><SONRQ><DTCLIENT>20200315112517<USERID>XXXXXXXX >> <USERPASS>XXXXXXXX >> <LANGUAGE>ENG<FI><ORG>USAA<FID>24591</FI><APPID>QWIN<APPVER>2300</SONRQ></SIGNONMSGSRQV1><CREDITCARDMSGSRQV1><CCSTMTTRNRQ><TRNUID>20200315112517<CLTCOOKIE>1<CCSTMTRQ><CCACCTFROM><ACCTID>XXXXXXXX</CCACCTFROM><INCTRAN><DTSTART>20200314000000<DTEND>20200315112517<INCLUDE>Y</INCTRAN></CCSTMTRQ></CCSTMTTRNRQ></CREDITCARDMSGSRQV1></OFX> >> >> >> Regards, >> John Ralls >> >>> On Mar 18, 2020, at 2:54 PM, Martin Preuss <[email protected]> wrote: >>> >>> Hi, >>> >>> please see my other mail (latest GIT). >>> >>> Maybe "103" then (I heard of some cases where "103" was necessary)? Or >>> perhaps "160"? >>> >>> Will fix the gui btw... >>> >>> >>> Regards >>> Martin >>> >>> Am 18.03.20 um 22:50 schrieb Chris Graves: >>>> Hi Martin, >>>> >>>> The GUI wouldn't let me leave that field blank, so I manually deleted >>>> the entry from the .conf file. Running again, it did use the defaults >>>> that you specified. However, still the http 400 error and no response. >>>> >>>> Sending: >>>> ------------------------------------- >>>> OFXHEADER:100 >>>> DATA:OFXSGML >>>> VERSION:102 >>>> SECURITY:NONE >>>> ENCODING:USASCII >>>> CHARSET:1252 >>>> COMPRESSION:NONE >>>> OLDFILEUID:NONE >>>> NEWFILEUID:20200318144035.000 >>>> >>>> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> Hi, >>>> >>>> not ATM, but that can be arranged. However, how about leaving that field >>>> empty in the settings dialog? That should default to 100 for OFXHEADER >>>> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had >>>> good^H^H^H reasons for those mixed defaults... :-}) >>>> >>>> Regards >>>> Martin >>>> >>>> >>>> Am 18.03.20 um 22:26 schrieb Chris Graves: >>>>> Nice! I see that the change has been made, but still receive the HTTP >>>>> 400 error. >>>>> >>>>> In the AQB5 ofx.log file for a successful case, I see >>>>> OFXHEADER:100 >>>>> VERSION:102 >>>>> >>>>> In the AQB6 file, I see >>>>> OFXHEADER:102 >>>>> VERSION:102 >>>>> >>>>> Not sure if this could be the problem. Is there a way to set >>>> OFXHEADER >>>>> and VERSION independently? >>>>> >>>>> >>>>> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss <[email protected] >>>> <mailto:[email protected]> >>>>> <mailto:[email protected] <mailto:[email protected]>>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> you can change the header manually to 102/103 in the >>>> homebanking setup >>>>> dialog (select user, edit user, switch to app settings and type-in >>>>> header version 102). >>>>> >>>>> Regards >>>>> Martin >>>>> >>>>> >>>>> Am 18.03.20 um 21:57 schrieb Chris Graves: >>>>>> Hi Martin, >>>>>> >>>>>> Looking better! However, to my knowledge, my bank only >>>> supports OFX >>>>>> version 102 or 103. I had been using 102. >>>>>> >>>>>> ofx.log: >>>>>> Sending: >>>>>> ------------------------------------- >>>>>> OFXHEADER:220 >>>>>> DATA:OFXSGML >>>>>> VERSION:220 >>>>>> SECURITY:NONE >>>>>> ENCODING:USASCII >>>>>> CHARSET:1252 >>>>>> COMPRESSION:NONE >>>>>> OLDFILEUID:NONE >>>>>> NEWFILEUID:20200318135033.000 >>>>>> >>>>>> <OFX> >>>>>> <SIGNONMSGSRQV1> >>>>>> <SONRQ> >>>>>> <DTCLIENT>20200318135025.000 >>>>>> >>>>>> On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss >>>> <[email protected] <mailto:[email protected]> >>>>> <mailto:[email protected] <mailto:[email protected]>> >>>>>> <mailto:[email protected] <mailto:[email protected]> >>>> <mailto:[email protected] <mailto:[email protected]>>>> wrote: >>>>>> >>>>>> Hi Chris, >>>>>> >>>>>> could you please test the latest GIT version? It should >>>> create >>>>> valid >>>>>> OFXv1 requests now, however, I can't test it completely >>>> since >>>>> I only >>>>>> have access to an OFXv2 server... >>>>>> >>>>>> >>>>>> Regards >>>>>> Martin >>>>>> >>>>>> >>>>>> Am 18.03.20 um 16:31 schrieb chris graves: >>>>>>> An additional bit of information from /tmp/ofx.log: >>>>>>> AQB5: >>>>>>> Sending: >>>>>>> ------------------------------------- >>>>>>> OFXHEADER:100 >>>>>>> DATA:OFXSGML >>>>>>> VERSION:102 >>>>>>> SECURITY:NONE >>>>>>> ENCODING:USASCII >>>>>>> CHARSET:1252 >>>>>>> COMPRESSION:NONE >>>>>>> OLDFILEUID:NONE >>>>>>> NEWFILEUID:20200318081757.000 >>>>>>> >>>>>>> <OFX>... >>>>>> [...] >>>>>> >>>>>> >>>>>> -- >>>>>> "Things are only impossible until they're not" >>>>>> >>>>> >>>>> >>>>> -- >>>>> "Things are only impossible until they're not" >>>>> >>>> >>>> >>>> -- >>>> "Things are only impossible until they're not" >>>> >>> >>> >>> -- >>> "Things are only impossible until they're not" >> > > > -- > "Things are only impossible until they're not" _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
