Hi,
>I don't understand what the issue is. If you get a 403, then the server
>is rejecting the update. HttpException indicates such a problem. It is
>often useful to distinguish authentication and HTTP issues from, say,
>parse errors.
I was just expecting that the execute signature of the method include
"execute() throws HTTPException {"
but I just noticed that the signature doesn't include "throws ARQException".
This must be a code design choice
of Jena.
Sorry for the disturbance.
VAÏSSE-LESTEVEN Arthur
________________________________
De : Andy Seaborne <[email protected]>
À : [email protected]
Envoyé le : Vendredi 30 août 2013 17h48
Objet : Re: SPARQL autentication and HTTP 403 error code
Arthur,
I don't understand what the issue is. If you get a 403, then the server
is rejecting the update. HttpException indicates such a problem. It is
often useful to distinguish authentication and HTTP issues from, say,
parse errors.
Andy
On 30/08/13 15:16, Arthur Vaïsse-Lesteven wrote:
> Hi,
>
> It seem that an error occurs when a proxy/server send a 403 HTTP status code
> in response to a SPARQL query.
>
> Stack trace begins by :
>
> org.apache.jena.atlas.web.HttpException: 403 - Forbidden
> at org.apache.jena.riot.web.HttpOp.exec(HttpOp.java:961)
> at org.apache.jena.riot.web.HttpOp.execHttpPostForm(HttpOp.java:711)
> at
>com.hp.hpl.jena.sparql.modify.UpdateProcessRemoteForm.execute(UpdateProcessRemoteForm.java:88)
> ...
>
> The code call done before this error is :
>
> [...]
>
> UpdateRequest update = UpdateFactory.create(query);
> UpdateProcessRemoteForm updateExecution =
>(UpdateProcessRemoteForm) UpdateExecutionFactory.createRemoteForm(update,
>update_endpoint_ip);
> updateExecution.setAuthentication(user_id,
>user_pwd.toCharArray());
> updateExecution.execute();
> [...]
> A possible fix may be the throw of a new ARQ exception in case of HTTPError
> reception.
>
> VAÏSSE-LESTEVEN Arthur.
>
