fc08681d89
1. Every text passage/label that appears in lessons must independent of the current language set for WebGoat.
2. Every lesson plan and solutions must be translated for each supported language.
Number 1 is achieved by using webgoat/util/WebgoatI18N.java and by having every output routed through this piece of code. You no longer say hints.add("Lesson Hint 1"); or ....addElement("Shopping Cart")) but you in the lesson you say hints.add(WebGoatI18N.get("Lesson Hint1")) or ....addElement(WebGoatI18N.get("Shopping Cart"). Then WebGoatI18N looks up the corresponding string for the language set as the current lanuage and returns it.
Number 2 is achieved by having subdirectories in lesson_plans corresponding to every language. That means, a lesson that has been translated to Spanish and German will be found in lesson_plans/English and lesson_plans/Spanish and lesson_plans/German.
This is how WebGoat finds out about available languages: in Course.java in loadResources() it looks for lesson plans.
Unlike before, now a lesson plan can be found multiple times in different "language" directories. So for every directory the lesson plan is found in, WebGoat associates this language with the lesson and also lets WebGoatI18N load the appropriate WebGoatLabels_$LANGAUGE$.properties file which contains the translations of labels.
So this is what you have to do for a new language:
First of all, you have to copy and translate every lesson plan that you need in the new language, and then you also have to create a WebGoatLabels_$LANGUAGE$.properties file with that labels that will be used in these lessons. Atm WebGoat crashes throws an exception when a label is missing but this can be sorted out quickly.
git-svn-id: http://webgoat.googlecode.com/svn/trunk@389 4033779f-a91e-0410-96ef-6bf7bf53c507
26 lines
1.3 KiB
HTML
26 lines
1.3 KiB
HTML
<div align="Center">
|
|
<p><b>Lesson Plan Title:</b> HttpOnly Test</p>
|
|
</div>
|
|
<p><b>Concept / Topic To Teach:</b></p>
|
|
<!-- Start Instructions -->
|
|
To help mitigate the cross site scripting threat, Microsoft has
|
|
introduced a new cookie attribute entitled 'HttpOnly.' If this flag is
|
|
set, then the browser should not allow client-side script to access the
|
|
cookie. Since the attribute is relatively new, several browsers neglect
|
|
to handle the new attribute properly.
|
|
<p>For a list of supported browsers see: <a href=http://www.owasp.org/index.php/HTTPOnly#Browsers_Supporting_HTTPOnly>OWASP HTTPOnly Support</a>
|
|
<p><b>General Goal(s):</b></p>
|
|
The purpose of this lesson is to test whether your browser supports the
|
|
HTTPOnly cookie flag. Note the value of the
|
|
<strong>unique2u</strong>
|
|
cookie. If your browser supports HTTPOnly, and you enable it for a
|
|
cookie, client side code should NOT be able to read OR write to that
|
|
cookie, but the browser can still send its value to the server. Some
|
|
browsers only prevent client side read access, but don't prevent write
|
|
access.
|
|
<br />
|
|
<br />
|
|
With the HTTPOnly attribute turned on, type
|
|
"javascript:alert(document.cookie)" in the browser address bar. Notice
|
|
all cookies are displayed except the unique2u cookie.
|
|
<!-- Stop Instructions --> |