the OFX specs show this example:
---------------------------------------------X8 POST http://www.fi.com/ofx.cgi HTTP/1.0 User-Agent:MyApp 5.0 Content-Type: application/x-ofx Content-Length: 1032 OFXHEADER:100 DATA:OFXSGML VERSION:160 SECURITY:TYPE1 ENCODING:USASCII CHARSET:NONE COMPRESSION:NONE NEWFILEUID:NONE OLDFILEUID:NONE <OFX> ... Open Financial Exchange requests ... </OFX> ---------------------------------------------X8 or, in a table: ---------------------------------------------X8 HTTP headers CRLF(s) MIME type information CRLF(s) OFX header element 1 CRLF OFX header element 2 CRLF OFX header element n CRLF(s) OFX SGML Block ---------------------------------------------X8 Well, the table isn't that helpfull... But the specs also state that all elements - http headers, OFX headers and OFX request - should be separated by a blank line from each other... Regards Martin -- "Things are only impossible until they're not" _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org 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.
