If queries are constrained by server side settings you are unlikely to be able to get around those simply by adding additional parameters to client requests.
For public endpoints it is normal to enforce limitations on requests to prevent users abusing the service and impacting upon other users. Rob On 27/04/2017 14:15, "Zak Mc Kracken" <[email protected]> wrote: Hi Andy, I would suggest to add these options, maybe I'll do it myself. The problem with wget is that certain server settings (I'm trying a Virtuoso endpoint) seem to limit the output and/or execution time that is granted to a web client (e.g., I cannot set a LIMIT bigger than 2000, I don't get so many results when I do). I was hoping that tools like rsparql can send headers to tell the server they're not a human-dedicated web interface, and was trying to rely on them rather than having to study the server rules. Thanks, Marco On 20/04/2017 12:38, Andy Seaborne wrote: > Marco, > > No - sorry, it isn't. What is possible is to use wget, with all its > options for auth, to send the query and send the output to "rset" for > result set parsing. > > wget will encode the query URL for you. > > Or modify s-query (which is in ruby). > > Andy > > On 19/04/17 10:31, Zak Mc Kracken wrote: >> Hi all, >> >> is it possible to use the Jena command line with the authentication >> facilities (http://jena.apache.org/documentation/query/http-auth.html)? >> >> I have an endpoint that is protected via HTTP Auth and I'd like to >> access it via rsparql. >> >> Thanks in advance, >> Marco >>
