I think what you're encountering is that popups are enabled not for TARGET URLs, but for SOURCE URLs.
In other words, enabling popups for "sis.nsd.org" means that if the Location header says "sis.nsd.org", it's allowed to open a pop-up (to wherever). What you seem to be wanting is for any Location to be able to open a pop-up, so long as it is to "sis.nsd.org", which is not (to my understanding anyway) how browser pop-up blocking works. D On Aug 22, 2014, at 5:17 PM, Ski Kacoroski <[email protected]> wrote: > Matt, > > Thanks for the answer, but I think I did not explain it well or I do > not understand what you are saying. I open a browser and enable popups > for https://sis.nsd.org. I login and popups work fine. I logout. I > then go to plain vanilla apache in the same browser window and click on > a link like: > > <a href="https://sis.nsd.org"; target="_blank">Synergy Login</a> > > It opens the app login window in a new tab, I login and popups do not > work. I close the tab and then right click on the link and say open in > new tab, login and popups work. > > So this is independent of the popup blocker as near as I can tell. > > cheers, > > ski > > On Fri, 22 Aug 2014 17:02:05 -0400 > Matt Simmons <[email protected]> wrote: > >> Hi Ski, >> >> So, from my reading of the code, there is a javascript function, >> DetectPopupBlockerOnLoad() that is called from the body onLoad. This >> function calls CheckForPopup(‘RT_POPUP’), a function that checks to >> see if there is a cookie present by the name of RT_POPUP. >> >> If the RT_POPUP cookie is present, then DetectPopupBlocker() runs >> which tries do a window.open() and, if it fails, returns a flag that >> indicates a popup blocker is in place, which then triggers the “you >> have a popup blocker” error. >> >> If the RT_POPUP cookie is not present, then the RT_POPUP cookie is >> created. >> >> In either case, DetectPopupBlockerOnLoad() returns false. >> >> If you’ll notice, if the RT_POPUP cookie is not present, at no point >> does it actually run the checks to see if a blocker is present. All >> it does is set the cookie. >> >> I would guess that, at some point in your application, you log out, >> and the application clears all browser cookies, rather than just the >> ones responsible for your account. If that’s the case, it would be >> responsible for the behavior flip-flopping. >> >> Someone more senior in javascript than me might be able to weigh in >> and provide a better evaluation, though. >> >> —Matt >> >> >> >> >> On Fri, Aug 22, 2014 at 4:45 PM, Ski Kacoroski <[email protected]> >> wrote: >> >>> Hi, >>> >>> Our new student records system uses a lot of popups. When we enter >>> in https://sis.nsd.org and allow popups it works perfectly. It >>> also works perfectly when I embed a link like: >>> >>> #1: <a href="https://sis.nsd.org";>Synergy Login</a> >>> >>> into a web page. However if I embed a link like: >>> >>> #2: > > >>> >>> the Synergy popup blocker and web browsers says popups are not >>> blocked, but we get popup blocked errors whenever it tries to open >>> a popup. >>> >>> Finally, if I right click on link #2 and open the application in a >>> new window or tab it works perfectly. >>> >>> Any ideas why this is happening? >>> >>> cheers, >>> >>> ski >>> >>> -- >>> "When we try to pick out anything by itself, we find it >>> connected to the entire universe" John Muir >>> >>> Chris "Ski" Kacoroski, [email protected], 206-501-9803 >>> or ski98033 on most IM services >>> >>> _______________________________________________ >>> Discuss mailing list >>> [email protected] >>> https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss >>> This list provided by the League of Professional System >>> Administrators http://lopsa.org/ >>> > > > > -- > "When we try to pick out anything by itself, we find it > connected to the entire universe" John Muir > > Chris "Ski" Kacoroski, [email protected], 206-501-9803 > or ski98033 on most IM services > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ -- I prefer to use encrypted mail. My public key fingerprint is FD6A 6990 F035 DE9E 3713 B4F1 661B 3AD6 D82A BBD0. You can download it here. Learn how to encrypt your email with the Email Self Defense guide.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
