Fix problem with newer gsoap versions. #125
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks. I'll have a look. |
|
@ellert can you get this fixed in EPEL 9 ? |
|
Does the version in EPEL work now? |
Yes, I've tested it yesterday. Thanks a lot for getting it in that quickly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The version of gsoap that comes with Rocky 9 does not call the request handlers in fparse.
The http_get handler never gets called on the server.
This causes clients to fail that use the REST API (voms-proxy-init3) as the server just terminates the connection without returning anything.
This is a quick patch that solves this by calling the http_get handler if fparse didn't.
This has only been tested on Rocky 9, but should also work on EL7/8 systems.