Page MenuHomePhabricator

Make test for setting "next" cookie more general
ClosedPublic

Authored by epriestley on Jan 9 2015, 12:24 AM.
Tags
None
Referenced Files
F14019149: D11292.id27130.diff
Tue, Nov 5, 9:37 PM
F13966212: D11292.diff
Wed, Oct 16, 6:58 AM
F13964910: D11292.id27130.diff
Tue, Oct 15, 10:39 PM
F13962699: D11292.id27142.diff
Tue, Oct 15, 11:46 AM
Unknown Object (File)
Sep 30 2024, 8:02 PM
Unknown Object (File)
Sep 24 2024, 10:03 PM
Unknown Object (File)
Sep 13 2024, 11:51 PM
Unknown Object (File)
Sep 13 2024, 11:49 PM

Details

Summary

Ref T6870. Since it does not make sense to redirect the user to the login form after they log in, we try not to set the login form as the next cookie.

However, the current check is hard-coded to /auth/start/, and the form can also be served at /login/. This has no real effect on normal users, but did make debugging T6870 confusing.

Instead of using a hard-coded path check, test if the controller was delegated to. If it was, store the URI. If it's handling the request without delegation, don't.

Test Plan
  • Visited login form at /login/ and /auth/start/, saw it not set a next URI.
  • Visited login form at /settings/ (while logged out), saw it set a next URI.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make test for setting "next" cookie more general.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
epriestley added a subscriber: lpriestley.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Jan 9 2015, 12:29 AM
This revision was automatically updated to reflect the committed changes.