Am 2015-03-15 um 15:15 schrieb Oleg Kalnichevski:
On Sat, 2015-03-14 at 23:01 +0100, Michael Osipov wrote:
Am 2015-03-13 um 18:05 schrieb Oleg Kalnichevski:
On Fri, 2015-03-13 at 15:49 +0100, Michael Osipov wrote:
...
That looks quite complex. Anyway, if you can think of a bit of
information that can uniquely identify the user in each scenario, the
problem is essentially solved. All we need is a token uniquely
representing user identity.
I am yet not completely sure about it but I guess that will resolve at
some point.
For now, I have created a little writeup which tracks all necessary
information for me:
http://people.apache.org/~michaelo/issues/HTTPCLIENT-1625/
If you think you can add valuable information, feel free to drop me some
lines.
We usually use project Wiki [1] for stuff like that. It also makes it
easier for other folks to contribute.
Oh, did not notice that. I'll migrate my Asciidoc file to that.
Unfortunately, it does not reuse my Apache Id, I have created a new
account over there. Please give the the appropriate permissions:
michael-o. I'll update HttpComponentsRoadmap and will create another
page for the issue.
One more thing: When an AuthScheme instance has completed the
authentication, can this object be reused? E.g., redirects on the same
server during one GET request.
It can be re-used and will automatically be re-used within the same
context (requests executed with the same instance of HttpContext).
This is what I have assumed. Thanks, I will note that and implement
accordingly.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
