Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your code needed a clean-up first. There's a bunch of errors in it if you do a test run. It's also a bit hard to read IMO.</p> <p>I've attached a working code sample below.</p> <pre><code>// Get users $input_pwd = ( isset( $_POST["password"] ) ? $_POST["password"] : '' ); $input_user = ( isset( $_POST["username"] ) ? $_POST["username"] : '' ); // Your pseudo database here ;) $usernames = array( "username@domain1.com", "username2@domain1.com", "username3@domain1.com", "username1@domain2.com", "/[a-z][A-Z][0-9]@domain2\.com/", // use an emtpy password string for each of these "/[^@]+@domain3\.com/" // entries if they don't need to authenticate ); $passwords = array( "password1", "password2", "password3", "password4", "", "" ); // Create an array of username literals or patterns and corresponding redirection targets $targets = array( "username@domain1.com" =&gt; "http://www.google.com", "username2@domain1.com" =&gt; "http://www.yahoo.com", "username3@domain1.com" =&gt; "http://www.stackoverflow.com", "username1@domain2.com" =&gt; "http://www.serverfault.com", "/[a-z][A-Z][0-9]@domain2\.com/" =&gt; "http://target-for-aA1-usertypes.com", "/[^@]+@domain3\.com/" =&gt; "http://target-for-all-domain3-users.com", "/.+/" =&gt; "http://default-target-if-all-else-fails.com", ); $logindata = array_combine( $usernames, $passwords ); if ( get_user_data( $input_user, $logindata ) === $input_pwd ) { session_start(); $_SESSION["username"] = $input_user; header('Location: ' . get_user_data( $input_user, $targets ) ); exit; } else { // Supplied username is invalid, or the corresponding password doesn't match header('Location: login.php?login_error=1'); exit; } function get_user_data ( $user, array $data ) { $retrieved = null; foreach ( $data as $user_pattern =&gt; $value ) { if ( ( $user_pattern[0] == '/' and preg_match( $user_pattern, $user ) ) or ( $user_pattern[0] != '/' and $user_pattern === $user) ) { $retrieved = $value; break; } } return $retrieved; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POPHP Regex String in Array
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UShashchange
    1. UShashchange
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPHP Regex String in Array
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks Michael, that is definitely much better laid out code. My problem is that even with this setup I am unable to type in any prefix before @domain.com and be redirected. Because I am still not a valid user. We have not defined the ability to validate any prefix at domain.com. Redirect, yes, but because not a valid user, we get thrown to an error page. At least that is as I have read it? Please correct me if I am wrong! Cheers.
      singulars
      1. PO
      1. USJames
    2. COYes, the code above redirects valid users to the target defined in the array. Invalid logins get sent off to the error page. That's how I read your code and your question ... Anyway, if you want to redirect invalid users as well, why don't you just call get_redirection_target when handling them, instead of sending them to 'login.php?login_error=1'?
      singulars
      1. PO
      1. UShashchange
    3. COCheers mate, basically my goal is to make any text included before a valid DOMAIN be accepted ON WHOLE as a valid username. Not to redirect invalid usernames. There are two parts to it, the redirection is spot on, the validating a domain name part is where I am now having trouble. If it cannot be done this way, I will take that on the chin. I just wish you could put some regex in the username array like [a-z][A-Z]@domain.com and have that work... Thank you for your efforts thus far!
      singulars
      1. PO
      1. USJames
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload