Allows the use of the Prez /sparql endpoint using POST method #169
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
…T method rather than GET. This supports larger SPARQL queries on Prez APIs that do not support long query args in GET requests.
hjohns
approved these changes
Jan 17, 2025
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.
Allows the use of the Prez /sparql passthrough endpoint using the POST method rather than GET.
This supports larger SPARQL queries on Prez APIs that do not support long query args in GET requests.
Fixes an issue on Azure APIM where it cannot accept an API route where the query param (/sparql?query=...) is longer than 2048 characters. It allows unlimited payload on POST.
I don't think this implementation is the cleanest way of doing it (all users of
useSparqlRequest()get both asparqlGetRequestfn and asparqlPostRequestfn, and can use whichever they prefer). But it is the method I used to get around the issue.This requires corresponding PR to be merged in backend Prez-api: RDFLib/prez#239