You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would put the main issue to be the 401, not the size.
Then to clarify that these are 2 separate issues. The size problem is when temporarily not using the basic auth option, which is something we did not invest time in and don't want to keep. So we are interested in the basic auth true option.
In simpler words:
when setGraphCrudUseBasicAuth=true => 401 for every request
when setGraphCrudUseBasicAuth=false => issue when size is large
assuming you have a well set up authenticated endpoint (sparql-auth endpoint in our case) and it is configured to work with basic auth, any request (e.g. a small select query) using the virtuoso apache client RdfStoreService implementation results in a 401.
Note that it is not tested directly with this library, but a2 0.7.0, which should be aligned as you pointed out.
Also note that recreating, in postman, the POST call that we saw this lib sending is also resulting in a 401.
(from @ssamarid)
Whenever
setGraphCrudUseBasicAuth=true
and SPARQL POST of datasets over 2000 triples ends up with 401.The problem does not manifest:
setGraphCrudUseBasicAuth=false
, orThe text was updated successfully, but these errors were encountered: