Re: Pre-emptive authorization

2019-01-03 Thread Karl Wright
Well, I don't actually see anything wrong with the idea of sending the auth header right up front and not requiring a whole extra back-and-forth to authorize. NTLM needs that but basic auth doesn't in theory. What is wrong with what they are doing? Do you have a spec I can present to them?

Re: Pre-emptive authorization

2019-01-03 Thread Michael Osipov
Am 2019-01-03 um 17:33 schrieb Karl Wright: Hi Oleg et al, One ManifoldCF user has an unusual requirement for basic auth that requires the auth header to be sent pre-emptively, not as a consequence of receiving a 401 response. He proposes the following patch for ManifoldCF, but I wonder

Pre-emptive authorization

2019-01-03 Thread Karl Wright
Hi Oleg et al, One ManifoldCF user has an unusual requirement for basic auth that requires the auth header to be sent pre-emptively, not as a consequence of receiving a 401 response. He proposes the following patch for ManifoldCF, but I wonder whether there's a better way to do this with

[jira] [Commented] (HTTPASYNC-146) Can't handle the response for the remote server send response and close connection

2019-01-03 Thread Oleg Kalnichevski (JIRA)
[ https://issues.apache.org/jira/browse/HTTPASYNC-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733106#comment-16733106 ] Oleg Kalnichevski commented on HTTPASYNC-146: - bq. Your original case need to call twice