I am having challenges to login with Girder available under HTTPS.
Related to the following change:
I don’t understand how I can give both the HTTPS
Authorization header and the Girder
Authorization headers at the same time. With Girder 2, I believe I had the following headers in my
api/v1/user/authentication request and it worked well:
Authorization=Basic myHTTPSBase64LoginPwd; Girder-Authorization=Basic myGirderBase64LoginPwd
If I do the same with Girder 3, Girder considers only
myHTTPSBase64LoginPwd and it ignores
I guess that should be an easy fix server side (use ‘Girder-Authorization’ if available in request headers). However, on the client side, should “Girder-Authorization” be sent if URL starts with HTTPS ?
What do you think ?