You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Rob Vesse (JIRA)" <ji...@apache.org> on 2013/04/16 19:19:16 UTC
[jira] [Created] (JENA-436) Support preserving cookie state over a
series of HTTP operations
Rob Vesse created JENA-436:
------------------------------
Summary: Support preserving cookie state over a series of HTTP operations
Key: JENA-436
URL: https://issues.apache.org/jira/browse/JENA-436
Project: Apache Jena
Issue Type: Improvement
Components: ARQ, Jena
Affects Versions: Jena 2.10.1
Reporter: Rob Vesse
Assignee: Rob Vesse
Priority: Minor
2.10.1 makes several improvements to HTTP operation handling to support authentication on updates. However the support for both queries and updates is still only for HTTP authentication which means it cannot be used with systems that use forms based authentication e.g. Apache mod_auth_form http://httpd.apache.org/docs/2.4/mod/mod_auth_form.html
Supporting this will require some fairly substantial reworking of the HTTP handling code for both queries and updates since it needs to support several things:
1 - Being able to carry out a login operation to an arbitrary URL to perform the authentication and initalize the necessary cookies
2 - Storing and presenting appropriate cookies over multiple requests
If we are to carry out this work it may be good to standardize to using a single HTTP library, currently queries use HttpQuery (a wrapper around the JRE provided HttpURLConnection) while updates use HttpOp (a wrapper around the Apache HttpClient library)
In doing this standardization we should also standardize how parameters are passed through these layers. For queries the QueryEngineHTTP sets properties on the HttpQuery object while for updates we pass them via a HttpContext object.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira