Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #16591 > unrolled thread

Automatically doing something if logged in

Back to article view | Back to comp.lang.php

Contents

  Automatically doing something if logged in bit-naughty@hotmail.com - 2016-02-22 10:02 -0800
    Re: Automatically doing something if logged in Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-22 14:04 -0500
    Re: Automatically doing something if logged in "J.O. Aho" <user@example.net> - 2016-02-22 20:21 +0100
      Re: Automatically doing something if logged in Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-22 14:52 -0500
        Re: Automatically doing something if logged in "J.O. Aho" <user@example.net> - 2016-02-23 06:58 +0100
      Re: Automatically doing something if logged in Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-22 22:25 +0100
        Re: Automatically doing something if logged in "J.O. Aho" <user@example.net> - 2016-02-23 07:04 +0100
          Re: Automatically doing something if logged in Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-23 08:31 +0100
        Re: Automatically doing something if logged in Arno Welzel <usenet@arnowelzel.de> - 2016-02-23 08:24 +0100
          Re: Automatically doing something if logged in Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-23 08:46 +0100
            Re: Automatically doing something if logged in Arno Welzel <usenet@arnowelzel.de> - 2016-02-23 11:36 +0100
              Re: Automatically doing something if logged in Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-23 21:02 +0100
      Re: Automatically doing something if logged in Arno Welzel <usenet@arnowelzel.de> - 2016-02-23 08:10 +0100

#16591 — Automatically doing something if logged in

Hi,
So say there's a forum site, and if there' been a reply to a post I've made, it sends me a link to that thread. If I click on it, and I've remained logged in when I was there last, then it *automatically takes me to that thread*. If I wasn't, then it shows me a Login box - when I log in it *automatically takes me to that thread*, but if I just went to the homepage NOT clicking on any email link, and I THEN log in, then it shows me something else (like "My homepage" or something), NOT that thread.
It's quite late, am I making sense? :)
How is this pulled off?

Like, the "login.html" page checks to see if the cookie is set? If it is, it takes me to that page directly? And if not, then it shows the "login box" with a ?threadid=something and then if the authentication is successful, then the login script checks to see if there's a "threadid" argument, and if so, redirects me to that page? This is how it *seems* to me intuitively, that it Should be coded, but how do I actually code it? :) Is there anything I'm missing?


Thanks for your help.

[toc] | [next] | [standalone]

#16592

On 2/22/2016 1:02 PM, bit-naughty@hotmail.com wrote:
> Hi,
> So say there's a forum site, and if there' been a reply to a post I've made, it sends me a link to that thread. If I click on it, and I've remained logged in when I was there last, then it *automatically takes me to that thread*. If I wasn't, then it shows me a Login box - when I log in it *automatically takes me to that thread*, but if I just went to the homepage NOT clicking on any email link, and I THEN log in, then it shows me something else (like "My homepage" or something), NOT that thread.
> It's quite late, am I making sense? :)
> How is this pulled off?
> 
> Like, the "login.html" page checks to see if the cookie is set? If it is, it takes me to that page directly? And if not, then it shows the "login box" with a ?threadid=something and then if the authentication is successful, then the login script checks to see if there's a "threadid" argument, and if so, redirects me to that page? This is how it *seems* to me intuitively, that it Should be coded, but how do I actually code it? :) Is there anything I'm missing?
> 
> 
> Thanks for your help.
> 

Well, when they click on a link to the forum thread, the page needs to
check to see if they are logged in or not.  If not, then it needs to
redirect to the login page.  Before the redirect, it could save the
eventual target several ways - it could be a parameter in the redirect,
for instance.  But more often it's a session or cookie value.  (In this
case a cookie value would not be a security risk because the link is
public, anyway).

Then, on a successful login, it gets the cookie or session value and
redirects to that page.

There are multiple ways to do this, but this is the basic flow.
-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#16593

On 02/22/2016 07:02 PM, bit-naughty@hotmail.com wrote:
> Hi,
> So say there's a forum site, and if there' been a reply to a post I've made, it sends me a link to that thread. If I click on it, and I've remained logged in when I was there last, then it *automatically takes me to that thread*. If I wasn't, then it shows me a Login box - when I log in it *automatically takes me to that thread*, but if I just went to the homepage NOT clicking on any email link, and I THEN log in, then it shows me something else (like "My homepage" or something), NOT that thread.
> It's quite late, am I making sense? :)
> How is this pulled off?

If you want things to happen "automagically", then you need to think
more than just PHP, add some javascript (there are loads of good
frameworks) and use websockets.


-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#16594

On 2/22/2016 2:21 PM, J.O. Aho wrote:
> On 02/22/2016 07:02 PM, bit-naughty@hotmail.com wrote:
>> Hi,
>> So say there's a forum site, and if there' been a reply to a post I've made, it sends me a link to that thread. If I click on it, and I've remained logged in when I was there last, then it *automatically takes me to that thread*. If I wasn't, then it shows me a Login box - when I log in it *automatically takes me to that thread*, but if I just went to the homepage NOT clicking on any email link, and I THEN log in, then it shows me something else (like "My homepage" or something), NOT that thread.
>> It's quite late, am I making sense? :)
>> How is this pulled off?
> 
> If you want things to happen "automagically", then you need to think
> more than just PHP, add some javascript (there are loads of good
> frameworks) and use websockets.
> 
> 

Actually, it can be done without a lot of trouble in PHP with the
appropriate tests and redirects.  No javascript, websockets or anything
else is required.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#16596

On 02/22/2016 08:52 PM, Jerry Stuckle wrote:
> On 2/22/2016 2:21 PM, J.O. Aho wrote:
>> On 02/22/2016 07:02 PM, bit-naughty@hotmail.com wrote:
>>> Hi,
>>> So say there's a forum site, and if there' been a reply to a post I've made, it sends me a link to that thread. If I click on it, and I've remained logged in when I was there last, then it *automatically takes me to that thread*. If I wasn't, then it shows me a Login box - when I log in it *automatically takes me to that thread*, but if I just went to the homepage NOT clicking on any email link, and I THEN log in, then it shows me something else (like "My homepage" or something), NOT that thread.
>>> It's quite late, am I making sense? :)
>>> How is this pulled off?
>>
>> If you want things to happen "automagically", then you need to think
>> more than just PHP, add some javascript (there are loads of good
>> frameworks) and use websockets.
>>
>>
> 
> Actually, it can be done without a lot of trouble in PHP with the
> appropriate tests and redirects.  No javascript, websockets or anything
> else is required.
> 

You are right. I was thinking a step further, where someone replied when
you was already logged in and was already at page X and needed a
redirect to page Y without the request of an user action.

-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#16595

J.O. Aho <user@example.net> wrote:

JFYI: Abuse of the example.net domain (and sibling second-level domains, and 
the “example” TLD) is disregarding the “Sender Address” section of the 
Acceptable Use Policy of news.individual.net and “may cause termination of 
access privileges without further notice.  Amounts paid will not be 
refunded, neither partly nor in full.”

<http://news.individual.net/rules.php>

(Individuals abusing the “.invalid” TLD instead, which is mistakenly 
recommended by that Usenet provider for everyday use with Usenet postings 
instead of only private testing, end up in my killfile automatically.)

<http://www.interhack.net/pubs/munging-harmful/>

> On 02/22/2016 07:02 PM, bit-naughty@hotmail.com wrote:
>> So say there's a forum site, and if there' been a reply to a post I've
>> made, it sends me a link to that thread. If I click on it, and I've
>> remained logged in when I was there last, then it *automatically takes me
>> to that thread*. If I wasn't, then it shows me a Login box - when I log
>> in it *automatically takes me to that thread*, but if I just went to the
>> homepage NOT clicking on any email link, and I THEN log in, then it shows
>> me something else (like "My homepage" or something), NOT that thread.
>> It's quite late, am I making sense? :) How is this pulled off?
> 
> If you want things to happen "automagically", then you need to think
> more than just PHP, add some javascript (there are loads of good
> frameworks)

ISTM that you have misunderstood the OP to mean that the viewport is 
automatically scrolled to the thread if they are logged in, have the forum 
displayed, and there are updates in that thread.  (Because I misunderstood 
it in the same way at first.)  But that is actually not what was being 
asked.

Instead, the OP wondered how following the same link in the same e-mail can 
have different outcomes depending on the login state, and how submitting a 
login form can have a different outcome if it was triggered by a link in an 
e-mail.

What probably happens here is that the URI of the link contains the 
thread/follow-up ID, and a cookie in the browser tells the forum/bulletin 
board application (phpBB?) about the login state of the user.  If the user 
was not logged in before, then a login form is displayed that contains 
hidden fields (“<input type="hidden" name="…" value="…">”) that are 
populated with the thread/follow-up ID.  The server-side script receiving 
the submitted form data then does the same as if the link URI had been used 
(presumably by server-side redirection) if the login is successful.  The 
login form is not populated with the thread/follow-up ID if the link is not 
used to navigate to the form, so “something else” is shown instead if the 
login is successful.


However, FWIW, following my comment on the use-case that you probably 
misunderstood from the OP:

There is no “javascript” [0], and there are lots of *bad* frameworks for 
client-side ECMAScript-based scripting.

Fortunately, a framework/library would be overkill here.

> and use websockets.

This is not a use-case where real-time updates are important and WebSocket 
would therefore be one of the preferred choices.  It suffices, for example, 
if the thread(s) is/are checked for relevant updates every 5 seconds.

Therefore, one should take into consideration that client-side support for 
WebSocket is still experimental [1] (and had been disabled in Firefox by 
default from version 4 to 23 inclusive [2]), and it might not be feasible
to use a framework for PHP like Ratchet [3] on that server or with that 
forum application.  So it is better to use XMLHttpRequest [4] for the time 
being (XML does not have to be used in the HTTP messages, JSON is more 
lightweight), and pull the server-side application for updates (GET) e.g. 
every 5 seconds.

___________
[0] <http://PointedEars.de/es-matrix>
[1] <https://developer.mozilla.org/en-US/docs/Web/API/WebSocket>
[2] <http://www.0xdeadbeef.com/weblog/2010/12/disabling-websockets-for-firefox-4/>
[3] <http://socketo.me/>
[4] <https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest>
-- 
PointedEars
Zend Certified PHP Engineer 
<http://www.zend.com/en/yellow-pages/ZEND024953> | Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#16597

On 02/22/2016 10:25 PM, Thomas 'PointedEars' Lahn wrote:
> J.O. Aho wrote:



> Therefore, one should take into consideration that client-side support for 
> WebSocket is still experimental [1] (and had been disabled in Firefox by 
> default from version 4 to 23 inclusive [2]),

Who cares about version 4 to 23, those ain't supported any more (end of
life), those who still use those old version deserve to get malware.
Current supported firefox versions are Firefox 38.6.1 ESR and Firefox
44.0.2.

-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#16600

J.O. Aho wrote:

> On 02/22/2016 10:25 PM, Thomas 'PointedEars' Lahn wrote:
>> Therefore, one should take into consideration that client-side support
>> for WebSocket is still experimental [1] (and had been disabled in Firefox
>> by default from version 4 to 23 inclusive [2]),
> 
> Who cares about version 4 to 23, those ain't supported any more (end of
> life), those who still use those old version deserve to get malware.

A Web application that does not work because an unwise design decision has 
been made is not malware.

> Current supported firefox versions are Firefox 38.6.1 ESR and Firefox
> 44.0.2.

Regardless, AISB, WebSocket support is still experimental in current browser 
versions, and unnecessary to leverage in the OP’s use-case as it has been 
misunderstood by you.

I also can see that, despite my friendly advice, you are continuing to 
disregard the AUP of your provider in a blatantly anti-social way.  *PLONK*

-- 
PointedEars
Zend Certified PHP Engineer 
<http://www.zend.com/en/yellow-pages/ZEND024953> | Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#16599

Thomas 'PointedEars' Lahn schrieb am 2016-02-22 um 22:25:

[...]
> Therefore, one should take into consideration that client-side support for 
> WebSocket is still experimental [1] (and had been disabled in Firefox by 
> default from version 4 to 23 inclusive [2]), and it might not be feasible

Yes, it is experimental. But at least since May 2014, when I created my
WebSocket example at <https://arnowelzel.de/tools/chat/>, all major
browsers (Firefox, Chrome, Internet Explorer and even most mobile
browsers) support it.

Also see <http://caniuse.com/#feat=websockets>

> to use a framework for PHP like Ratchet [3] on that server or with that 
> forum application.  So it is better to use XMLHttpRequest [4] for the time 
> being (XML does not have to be used in the HTTP messages, JSON is more 
> lightweight), and pull the server-side application for updates (GET) e.g. 
> every 5 seconds.

ACK. XHR is easier to implement.


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#16601

Arno Welzel wrote:

> Thomas 'PointedEars' Lahn schrieb am 2016-02-22 um 22:25:
> [...]
>> Therefore, one should take into consideration that client-side support
>> for WebSocket is still experimental [1] (and had been disabled in Firefox
>> by default from version 4 to 23 inclusive [2]), and it might not be
>> feasible
> 
> Yes, it is experimental. But at least since May 2014, when I created my
> WebSocket example at <https://arnowelzel.de/tools/chat/>, all major
> browsers (Firefox, Chrome, Internet Explorer and even most mobile
> browsers) support it.
> 
> Also see <http://caniuse.com/#feat=websockets>

So it is not supported in Opera Mini 8 with a global market share of 4.79 %. 
Users of browsers that someone did not define as “major” are not important 
enough?

-- 
PointedEars
Zend Certified PHP Engineer 
<http://www.zend.com/en/yellow-pages/ZEND024953> | Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#16602

Thomas 'PointedEars' Lahn schrieb am 2016-02-23 um 08:46:

> Arno Welzel wrote:
> 
>> Thomas 'PointedEars' Lahn schrieb am 2016-02-22 um 22:25:
>> [...]
>>> Therefore, one should take into consideration that client-side support
>>> for WebSocket is still experimental [1] (and had been disabled in Firefox
>>> by default from version 4 to 23 inclusive [2]), and it might not be
>>> feasible
>>
>> Yes, it is experimental. But at least since May 2014, when I created my
>> WebSocket example at <https://arnowelzel.de/tools/chat/>, all major
>> browsers (Firefox, Chrome, Internet Explorer and even most mobile
>> browsers) support it.
>>
>> Also see <http://caniuse.com/#feat=websockets>
> 
> So it is not supported in Opera Mini 8 with a global market share of 4.79 %. 
> Users of browsers that someone did not define as “major” are not important 
> enough?

I wouldn't call a browser which is used by less then 5% of all users a
"major" browser.

But since WebSockets and not supported *everywhere* I already agreed to
you that I would use XHR instead if it is important that most people can
use the application.


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#16603

Arno Welzel wrote:

> Thomas 'PointedEars' Lahn schrieb am 2016-02-23 um 08:46:
>> Arno Welzel wrote:
>>> Also see <http://caniuse.com/#feat=websockets>
>> So it is not supported in Opera Mini 8 with a global market share of 4.79
>> %. Users of browsers that someone did not define as “major” are not
>> important enough?
> 
> I wouldn't call a browser which is used by less then 5% of all users a
> "major" browser.

Interesting.  Note that the numbers are misleading because among mobile 
devices, Opera currently has a market share of 10.91 % according to 
StatCounter.  That would probably include Opera Mini 8, whereas at Opera 34 
is listed at caniuse.com as the current version to have a market share of 
0.68 %.  So there is reason to be more careful in one’s analysis and design 
decisions.
 
> But since WebSockets and not supported *everywhere* I already agreed to
> you that I would use XHR instead if it is important that most people can
> use the application.

I have noticed it, but I want to point out that I did not explicitly 
recommend *in general* to use XHR *instead*.  Anyhow, ISTM we are off-topic 
now.

-- 
PointedEars
Zend Certified PHP Engineer 
<http://www.zend.com/en/yellow-pages/ZEND024953> | Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#16598

J.O. Aho schrieb am 2016-02-22 um 20:21:

> On 02/22/2016 07:02 PM, bit-naughty@hotmail.com wrote:
>> Hi,
>> So say there's a forum site, and if there' been a reply to a post I've made, it sends me a link to that thread. If I click on it, and I've remained logged in when I was there last, then it *automatically takes me to that thread*. If I wasn't, then it shows me a Login box - when I log in it *automatically takes me to that thread*, but if I just went to the homepage NOT clicking on any email link, and I THEN log in, then it shows me something else (like "My homepage" or something), NOT that thread.
>> It's quite late, am I making sense? :)
>> How is this pulled off?
> 
> If you want things to happen "automagically", then you need to think
> more than just PHP, add some javascript (there are loads of good
> frameworks) and use websockets.

This is not required at all. Just add the desired target after the login
as a parameter to the login page or set a cookie which will be used by
the login page to redirect to the target after successful login etc..


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.php

csiph-web