: Hi Cyb
: Many thanks for taking the time to reply. The solutions are clearly
: not as simple as I had hoped for.
: : When dealing with your webpage, there are two kinds of programming:
: : server-side and client-side.
: : client-side. When the page is loaded on the user's computer, the
: : etc) and executed.
: : Server-side code is executed on the server. When the user's browser
: : requests a page, the page request is sent to the server. The server
: : then executes any code associated with that page (as well as code
: : associated with the website, etc), and returns a stream of HTML
: : which the user's browser interprets as a "web page".
: : When the user's browser sends a request to the server, it sends
: : other information, including any cookies (small files of information
: : set by the website) or form values. Using server-side code, you can
: : individual users, their logged in status, their logged in level (or,
: : which pages they are allowed to access), etc.
: : There are several server-side languages to choose from depending on
: : your server's operating system. If you are using a linux or unix
: : system, php and perl are popular choices. If you are using Windows,
: : php is still an option, but I would recommend you get Microsoft's
: : asp.net. They have recently begun providing a free version which can
: : handle most basic scenarios, including password protected sites.
: : The next step would be to look into getting a database server to
: : store all those usernames and passwords... :)
: : -cyb
This is a good example of audience. Here is a list of universal, industry-standard codes: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
You may want to get with your administrator or provider about
how these techniques may be applied. Redirects are mentioned
several time, yet not a hint of authentication. 404 are
the most regularly achieved responses behind 200