Monday, March 02, 2009
Find Articles/e-Link scripting error
The problem
You click e-Link to find full text to an article, and you get this error message:
"NoScript filtered a potential cross-site scripting (XSS) attempt from [http://salak.cc.columbia.edu:8332]. Technical details have been logged to this console." (ref01)
Recreate the problem
The workaround
Click on the pop-up blocker message and allow "unsafe reload," which will allow e-Link to do its job.
fyi
This problem occurred in Firefox. I did not confirm it in IE.
It is a problem at the public workstations in reference, not at the reference desk, and probably not on anyone's office computer.
You click e-Link to find full text to an article, and you get this error message:
"NoScript filtered a potential cross-site scripting (XSS) attempt from [http://salak.cc.columbia.edu:8332]. Technical details have been logged to this console." (ref01)
Recreate the problem
- On the databases page, type
into the Find Articles (not Find Databases) box. Use the General/Multidisciplinary default. Click enter. - Click the title, "A blend of help and hassle." (I don't know if the link I provided will time out or not.)
- Click the blue e-Link arrow. See error message.
The workaround
Click on the pop-up blocker message and allow "unsafe reload," which will allow e-Link to do its job.
fyi
This problem occurred in Firefox. I did not confirm it in IE.
It is a problem at the public workstations in reference, not at the reference desk, and probably not on anyone's office computer.
Labels: e-link, find articles, reference ghost
// posted by Jenna @ 4:34 PM 
Comments:
<< Home
"NoScript filtered a potential cross-site scripting (XSS) attempt from [http://salak.cc.columbia.edu:8332]. Technical details have been logged to this console." (ref01)
Thanks for finding this!It's actually a larger issue, referring to the entire .cc.columbia.edu:8332 address
(which includes Sakai). I have addressed it on Ref9, and will apply the same fix on the rest of the REF's as soon as possible.
eb
Post a Comment
Thanks for finding this!It's actually a larger issue, referring to the entire .cc.columbia.edu:8332 address
(which includes Sakai). I have addressed it on Ref9, and will apply the same fix on the rest of the REF's as soon as possible.
eb
<< Home
