authentication - Chrome basic auth and digest auth issue -
i'm having issues chrome canceling http requests , i'm suspecting cached authentication data cause. let me first write down important factors application i'm writing.
- i using basic authentication scheme time guard several services , resources in web app.
- in meantime using/testing app heavily using chrome main google account synced. using name - "lukasz" - username in basic auth.
- recently have switched application use digest authentication.
- now, of http requests i'm making failing
status=failed
no apparent reason. happens when i'm using user "lukasz", if enter other unique username - there no problem.
i looked everywhere in backend , frontend , couldn't locate issue in our code. can reproduce user "lukasz" each time. reverted code basic auth (while not touching rest of app) , problem gone.
that led me think there wrong cached passwords. cleared cache in chrome, didn't help. after several hours of analyzing issue decided make sure i'm running fresh instance of chrome, reinstalled (deleting disk data along way). tadaaa! problem gone , couldn't reproduce anymore. synchronized google account newly installed chrome , after short while the requests app started failing again!! took deeper @ (cleaning profile data disk , redoing steps) , indeed looks problem starts account synced cloud!
yes, know sounds dodgy. sounds ridiculous. sounds stupid. sure 2 problems somehow related (failing requests , account sync).
my idea this: chrome somehow remembered using "lukasz/my-pass" basic auth services. after switched digest auth same combination of credentials (lukasz/my-pass) acting funny. perhaps under hood chrome still thinks basic auth , cancels requests when learns otherwise?
update: i've did low level debugging chrome://net-internals/
, appears problem while reading cache entry. seems prove initial assumption. did investigation , found this article. apparently adding "last-modified" header http response has solved issue in chrome (i'm still having problems in ff, that's off topic). however, still doesn't solve issue entirely. why requests failing in first place?
you try using incognito mode , see happens. may give hints without having clear cache or re-installing chrome.
also take @ how clear basic authentication details in chrome
Comments
Post a Comment