If the question you wanted to ask isn't covered here, then please check the other documentation as well. In particular, the rough guide covers most of the basic elements of the publishing service.
| Tag | Description | Example |
| $Date$ | The version's date | 2009/01/29 13:09:03 |
| $Revision$ | The revision of the file | 1.31 |
These tags work because the web server is implemented on top of CVS. In fact, you can use any keyword which is supported by CVS in your documents. However, only those listed above are likely to produce meaningful results.
To control access you need to create a file called .htaccess (note the leading dot) in the directory that you want to restrict. This will impose restrictions on this directory, and all of the levels below it.
To restrict users based on the IP address that they're connecting from, you need to use something like:
deny from all allow from 129.215.0.0/16
This example would restrict access to all machines within the University's network, ie within .ed.ac.uk. However, it would exclude the student accommodation network (ResNet), to allow these machines to see that pages too, add the following line to the end:
allow from 10.0.0.0/8Remember that IP address based restrictions are by no means 100% secure, especially as the number of machines you allow access to increases. Also, any IP restricted area of the site is still visible to those with Informatics Publishing user names and passwords.
If you wish to protect your documents so that a username and password are required to view them, then use these lines as an example:
CosignProtected on AuthType Cosign Require user neilb rwb AuthGroupFile /liveroot/conf/access/group.capabilities AuthzUserAuthoritative off Require group web/wwwinf/staffonlyThe first 3 lines would be enough to restrict the pages to the DICE users "neilb" and "rwb". With the addition of the last three lines, then any DICE user with teh "web/wwwinf/staffonly" capabilility would also have access. Contact support if more complicated restrictions are required.
#include virtual form of SSI eg:
<!--#include virtual="/research/games/header.inc"--> <!--#include virtual="/research/games/navigation.inc"-->
/research/games/header.inc file above must look something
like:
<!--START:/research/games/header.inc--> [The content goes here] <!--END:/research/games/header.inc-->Note that the START and END specify the location of this .inc file.
This means that if you have a web page containing an email address (useful when telling someone how to get in contact), then its likely that the address will start receiving junk mail.
When including an email address on a web page, try to disguise the fact that its an email address. Humans should still be able to recognise it, but programs that go around looking for them will probably not. So rather than putting "send mail to SomeAddress@inf.ed.ac.uk" on your web page, do "send mail to SomeAddress (at) inf . ed . ac . uk", it looks a little clumsy, but people should know what you mean, and it should throw most automated harversters off the scent.
You can go further by using convoluted HTML to obfuscate things, eg "send mail to SomeAddress@inf.ed.ac.uk"
Which actually looks like this in HTML:
send mail to <a href="mailto:SomeAddress@inf.ed.ac.uk">SomeAddress@inf.ed.ac.uk</a>
This example also use the mailto: URL in the <A> tag. This is usually an even more sure fire way of the harvesting programs finding real email addresses, however if you must use it, you can still try to confuse things by using numerical entities as in the above example.
None of this tricks will guarantee that the address won't be harvested, but they should help.
& character is
special in HTML and marks the beginning of an entity. You need to
replace any occurance of & with the string
&.
|
Informatics Forum, 10 Crichton Street, Edinburgh, EH8 9AB, Scotland, UK
Tel: +44 131 651 5661, Fax: +44 131 651 1426, E-mail: school-office@inf.ed.ac.uk Please contact our webadmin with any comments or corrections. Unless explicitly stated otherwise, all material is copyright © The University of Edinburgh |