Closed strk closed 8 years ago
It's currently done as part of login()
in order to "Load a page to get the new cookies". It might not be required on all Trac versions or even all authentication types.
How about just checking if the "trac_auth" cookie exists after the first call ? I see the setCookie header sent in response to the /login action already.
I dropped that get("/") in my sandbox without any issues, I'll try at work, we use a reverse-proxy for auth, if that works fine then we should be able to drop it.
Dropping the get("/") worked for me too, against trac 1.0.5
I pushed the removal of that extra get.
Adding debugging lines I see three GET requests being performed before starting the editor:
NOTE: the third one is modified as per #12 to reduce the size of returned page.
I understand the first one (which would ideally be avoided by storing cookies offline, see #13), but what's the second one for ?