Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Server type return in HTTP header is not Corese #184

Open
MaillPierre opened this issue Apr 23, 2024 · 0 comments
Open

[Bug] Server type return in HTTP header is not Corese #184

MaillPierre opened this issue Apr 23, 2024 · 0 comments

Comments

@MaillPierre
Copy link
Contributor

Issue Description:

The server type return in the HTTP header of SPARQL query responses is not related to Corese

Steps to Reproduce:

  1. Create an empty file "test.ttl"
  2. Create a query file "query.rq" containing:
SELECT DISTINCT ?server ?serverGet {
    SERVICE <https://corese.inria.fr/sparql?mode=report> {
        {
            SELECT * {
                ?s ?p ?o
            } LIMIT 1
        }
    }
    values (?_service_report_0 ){
        (UNDEF )
    }
    BIND( js:server() AS ?server)
    BIND( xt:get(?_service_report_0, "server") AS ?serverGet)
}
  1. Use Corese-command such as java -jar corese-command-4.5.0.jar sparql -i test.ttl -q query.rq -o result.csv -of csv
  2. Server type appears in result.csv

Expected Behavior:

A result with a relation to Corese is expected, such as:

server,serverGet,_service_report_0
corese,corese/4.5.0,_j_4

Actual Behavior:
The result obtained are related to the NGinx web server:

server,serverGet,_service_report_0
nginx,nginx/1.12.1,_j_4

Note to Developers:

The headers should probably be adapted depending on the response data type requested. text/html could still return NGinx, but any RDF-related type should indicate the type of SPARQL server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant