Version 5.1.3 published
Hi Chris I confirm that adding both parameters to the partnership the ‘chunking’ is disabled. Since this is the first partner that has this problem, I don’t think it’s a major issue. For your information, they use “eBiss 2016” as software, that is quite an old version and maybe that is the issue. If you manage to find a way to disable the chunking without imposing a limit would be nice, but don’t lose too much sleep on it. Thanks for your support. Davide From: discussion@openas2.p.re.sourceforge.net...
Ah, I didn't tried that, ok, good to know. D. On January 25, 2024 10:58:28 PM GMT+01:00, Christopher Broderick uhurusurfa@users.sourceforge.net wrote: Just tested and it sets the Transfer-Encoding to chunked if you do not have the "no_chunked_max_size" attribute set to something. I will look into how to get Apache HTTP client not to set the header but the workaround is to add something like this to your partnership: <attribute name="no_chunked_max_size" value="104857600"/> Disable "Transfer-Encoding:...
Hi, This week we (plurale majestatis) started the configuration of a new AS2 customer, it turned out their system doesn't support "chunked" transfer, so I added the 'prevent_chunking' option in the partnership. However, this doesn't seems to work as advertised, the "content-length" is added to the header, but the "transfer encoding" header is still present: Headers: Content-Type: application/edifact Content-Length: 3574 Date: Thu, 25 Jan 2024 08:46:29 +0100 From: team@kpn-messaging.net Message-ID:...
Hi Chris, Ok, one step forward, after letting the system reload the configuration, the Poller was still working, however, I tryied to send a message with a wrong partnership and it failed to 'move' the message to the 'error' directory, the message was copied, but not removed from the outgoing directory: 2022-12-27 11:00:22.693 ERROR OpenAS2Exception: Error occurred:: Partnership not found: Partnership null Sender IDs = {as2_id=mycompanyAS2} Receiver IDs = {as2_id=mendelsontestAS2} Attributes = {}...
Ok, I'll install it on my backup server and try it out.
ADDENDUM: I just tested the backup server, that I had reconfigured like the "production one" but not tested, and even on that machine the Poller had stopped working. So at least the behavour is consistent. Davide
Hi Chris, No, I am using the "old" style config, so there is just one poller and all the partnerships are using the same directory. Yeah, normally I do force the reload every time, but this time I decided to 'try it'... and well... Exact steps... just changed the partnership configuration to point to the 'new' certificate (basically changed the x509alias on all the interested partners with a sed 's|...|' -i) and then wait for the "reload" message in the log. I realized the poller wasn't polling anymore...