Sure, I have just triggered a new build. Sorry for the hassle.
Hi,
Will you push again this one? It fixes an issue I have compiling with boost serialization in Fedora 32.
Good catch. I'll fix that after the Christmas break.
This update has been unpushed.
Works well
Runs well for us too.
Looks alright now, thanks!
Hello again,
Sorry I need to downvote this update, but it looks like the commit 34813cc29eaa519482626a3c3576f5f7708653a6 introduced a change that breaks the interaction with Bestman endpoints.
Specifically these lines https://github.com/globus/globus-toolkit/commit/34813cc29eaa519482626a3c3576f5f7708653a6#diff-3a9f71c771ae39d522a3ef8e9dbe4162L519
They removed SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS, and Bestman doesn't seem to like empty fragments. It ends with a "0" prepended to the actual payload, which results on things like
HTTP/1.1 501 Method 0POST is not defined in RFC 2068 and is not supported by the Servlet API
Granted, this is an issue with Bestman, no the package itself, but if this goes into production, then all transfers to/from Bestman endpoints are going to break.
Also, Bestman is on it's EOL, so it is unlikely this will get patched. Do you think this could be re-enabled for the moment being?
Regards.
Hello again,
Sorry I need to downvote this update, but it looks like the commit 34813cc29eaa519482626a3c3576f5f7708653a6 introduced a change that breaks the interaction with Bestman endpoints.
Specifically these lines https://github.com/globus/globus-toolkit/commit/34813cc29eaa519482626a3c3576f5f7708653a6#diff-3a9f71c771ae39d522a3ef8e9dbe4162L519
They removed SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS, and Bestman doesn't seem to like empty fragments. It ends with a "0" prepended to the actual payload, which results on things like
HTTP/1.1 501 Method 0POST is not defined in RFC 2068 and is not supported by the Servlet API
Granted, this is an issue with Bestman, no the package itself, but if this goes into production, then all transfers to/from Bestman endpoints are going to break.
Also, Bestman is on it's EOL, so it is unlikely this will get patched. Do you think this could be re-enabled for the moment being?
Regards.
Thanks for the heads up and sorry for the trouble. I can not push a build myself, but I have let them know
https://bugzilla.redhat.com/show_bug.cgi?id=2272359