Students can collect their exams and request for on-spot regrade from SAL 339 on Monday, May the 11th. The time for the exam collection for each section is as follows:
Section 1: 12:00 PM to 2:00PM
Exams for the DEN students who took the exam on campus shall be posted in their web accounts tomorrow. They can clarify their doubts by emailing their
questions to TA. Shahzad Tiwana or can also come physically to SAL 339 during the allocated time.
Section 2: 2:00 PM to 4:00 PM
Please note this is the "ONLY" chance for you to collect your final exams. If for some reason
a student in section 1 time slot cannot make it to TA office, he/she can come and collect it during Section 2 time slot and vice versa.
We will allow the use of "AltaVista" to replace
"Google" search, for students that are still finding problems with
being denied access. The string to look for there is "Sponsored
Matches". If you do use AltaVista instead of Google, please show it properly
in the "result page, so that the graders can check the appropriate search
engine.
More on homework 7
PROXIES
Some sites use proxies to go through fire wall machines, or just as
cache in order to improve performance. Proxies can also be used for
accessing resources through protocols not supported directly (or
supported badly :-) by the libwww-perl library.
You should initialize your proxy setting before you start sending
requests:
use LWP::UserAgent;
$ua = new LWP::UserAgent;
$ua->env_proxy; # initialize from environment variables
# or
$ua->proxy(ftp => 'http://proxy.myorg.com');
$ua->proxy(wais => 'http://proxy.myorg.com');
$ua->no_proxy(qw(no se fi));
my $req = new HTTP::Request 'wais://xxx.com/';
print $ua->request($req)->as_string;
The LWP::Simple interface will call env_proxy() for you automatically.
Applications that use the $ua->env_proxy() method will normally not use
the $ua->proxy() and $ua->no_proxy() methods.
Some proxies also require that you send it a username/password in order
to let requests through. You should be able to add the required header,
with something like this:
use LWP::UserAgent;
$ua = new LWP::UserAgent;
$ua->proxy(['http', 'ftp'] => 'http://proxy.myorg.com');
$req = new HTTP::Request 'GET',"http://www.perl.com";
$req->proxy_authorization_basic("proxy_user", "proxy_password");
$res = $ua->request($req);
print $res->content if $res->is_success;
Replace `proxy.myorg.com', `proxy_user' and `proxy_password' with
something suitable for your site.
Clarification regarding the requirement NOT to use "getElementByTagName" function
In the assignment description is says:
"You must make sure to write your program so it does not explicitly make use
of the tag names in the sample XML file mentioned above." (end of page 4)
This means that you should NOT use the "getElementByTagName" function in
your program.
The main reason for this requirement is to encourage you to develop
a program with enough flexibility to allow changing the tag names at
any point without having to go back and revising/rewriting the code.
Account Quota Increased
Account quota of all the students have been increased from 50MB to 150MB.
Scheduled server downtime
The server will be down on 2/7 from 6:00am to 12:00pm for a scheduled maintenance.
More information can be found on the ITS site http://www.usc.edu/its.
TA Office Hours on January 23rd 09
TA office hours on January 23rd 09 shall be held from 1 PM till 4PM instead of the time posted on the class website.
Cross Side Scripting Problem (XSS) in Firefox -- Post by Shahzad
Some of the students may find that their code works correctly in Firefox
if they are accessing all the XML files locally from their machines, but
get "Permission denied" error, if the same files are accessed from course
website. This is because the script, lying on your machine, is trying to
act upon a file that is hosted on another domain. This is called cross
side scripting which is not allowed in browsers. It turns out that Firefox's
implementation is more restrictive as compared to IE, when it comes to
XSS. So, please make sure, when you are testing your implementation, either both the
HTML/Javascript file and the XML file are on your local machine or both the files are on your course unix account.
Emailing TAs
Please make sure to include emails addresses of "ALL" four TAs, if you need any clarification or help.
SUBMIT Command
***JUST IN***
The previous reported issue has been resolved. The SUBMIT command should
be executed from csci571.usc.edu.
UNIX Information
For the students that have never seen UNIX before, here are a few links with useful information:
General information on operating systems, productivity applications,
Internet connectivity, e-mail and web publishing at USC, can be found
at the
ISD Help site.
Getting rid of the USC Disclaimer
To get rid of the USC Disclaimer which appears at the bottom of each
web page, place a NOSCRIPT tag immediately before the /BODY tag.
<NOSCRIPT>
</BODY>
Some people have found that the suggestion of using the <NOSCRIPT> tag at
the end of the HTML file does not work if they have lines such as
writeln("</BODY>") in their JavaScript code. Another way to get rid
of the USC disclaimer is to use this code at the beginning of the HTML
file, right after the closing </HEAD> tag:
<!--
<BODY>
<div style="display: block; font-family: Verdana, Geneva, Arial;
font-size: 10px">
The University of Southern California does not screen or control the
content on this website and thus does not guarantee the accuracy,
integrity, or quality of such content. All content on this website is
provided by and is the sole responsibility of the person from which
such content originated, and such content does not necessarily reflect
the opinions of the University administration or the Board of Trustees
</div>
<div style="display: block; font-family: Verdana, Geneva, Arial;
font-size: 10px">
The University of Southern California does not screen or control the
content on this website and thus does not guarantee the accuracy,
integrity, or quality of such content. All content on this website is
provided by and is the sole responsibility of the person from which
such content originated, and such content does not necessarily reflect
the opinions of the University administration or the Board of Trustees
</div>
</BODY>
//-->
Notice that to avoid showing the USC disclaimer on this page in
between the code above, I had to add the same code at the beginning of
this file (you can View Source this page to check this out).
Late Assignment Policy
Homework submitted for grading before or on the "Homework Due Date", as listed
in the Schedule of Lectures, will be eligible for 100% of the grade points for
the assignment. Homework submitted late will be accepted for up to 7 calendar
days after the due date, and will receive an automatic 10% penalty. Homework
submitted more than 7 days after the due date will not be accepted.
Accounts for on-campus and DEN students
If you are a remote student, you may get an account on a USC machine or use a
corporate or personal web site. To arrange for a USC
computer account, connect to the DEN web site at http://den.usc.edu/.
On campus students need to establish a directory in which they can store web
pages that will be delivered by USC's student web server. Complete
instructions on how to do this can be found at
http://www.usc.edu/uscweb/authoring/ppages.html.
csci571 server
If you are not using a personal or corporate account, but are using the
USC machines, then please do your assignments only on the server
assigned for you.
Students in all sections: ssh to csci571.usc.edu
Port Assignment Policy
To ensure that the possible collisions of TCP/IP ports among students are minimized, please
follow the following port assignment methodology, based on the last 5 digits
(XXXXX) of the random number that was assigned to you when you signed up the
class list:
Use Instead of
XXXXX: Apache port 80 (HTTP port)
XXXXX+1: Tomcat port 8080 (HTTP port)
XXXXX+2: Tomcat port 8005 (admin shutdown port)
XXXXX+3: Tomcat port 8009 (Apache jk port)
XXXXX+4: MySQL port 3306 (TCP/IP port)
Please replace the default ports with the above numbered ports.
