Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on May 14, 2018. It is now read-only.

Update RedirectionStrategy.php#276

Closed
olexp wants to merge 1 commit into
bjyoungblood:masterfrom
olexp:patch-1
Closed

Update RedirectionStrategy.php#276
olexp wants to merge 1 commit into
bjyoungblood:masterfrom
olexp:patch-1

Conversation

@olexp

@olexp olexp commented Jan 9, 2015

Copy link
Copy Markdown
  1. Skip redirection for authenticated users
    It is confusing that user is redirected to login page while he is already authenticated. And usually this leads to another redirection (login redirects to default login page).
  2. Add query parameter 'redirect' that defines a URL for redirection after successful login.
    This parameter is used in ZfcUser by default. Corresponding field (addQueryRedirect) is added to object to control adding.

1. Skip redirection for authenticated users
It is confusing that user is redirected to login page while he is already authenticated. And usually this leads to another redirection (login redirects to default login page).
2. Add query parameter 'redirect' that defines a URL for redirection after successful login.
This parameter is used in ZfcUser by default. Corresponding field (addQueryRedirect) is added to object to control adding.
@Ocramius

Ocramius commented Jan 9, 2015

Copy link
Copy Markdown
Contributor

This won't be merged:

  • auto-redirect causes security issues
  • tests are missing
  • the module doesn't have anything to do with authentication, and therefore should stay far from the domain of authentication (module is about authorization instead)

@olexp olexp deleted the patch-1 branch January 9, 2015 16:25
@Ocramius

Ocramius commented Jan 9, 2015

Copy link
Copy Markdown
Contributor

@olexp consider creating a custom redirect strategy that fits your own domain. Linking ZF-Commons/ZfcUser#487 for reference

@olexp

olexp commented Jan 9, 2015

Copy link
Copy Markdown
Author

The second part seems to be already covered by pull request #225. Sorry about that.

Thanks for commenting. I'll add another strategy as you propose.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants