You are looking at the HTML representation of the XML format.
HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format.
To see the non HTML representation of the XML format, set format=xml.
See the complete documentation, or API help for more information.
<?xml version="1.0"?>
<api>
  <query-continue>
    <allpages gapcontinue="Running_dropbox_on_central_servers" />
  </query-continue>
  <query>
    <pages>
      <page pageid="837" ns="0" title="Read/write MAC disk on Ubuntu">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">There is not a beautiful solution for this, as the hfsplus filessytem doesn't support &lt;code&gt;uid&lt;/code&gt; and &lt;code&gt;gid&lt;/code&gt; mount options. So a hacky workaround would be the following.

Be sure you only have '''one''' Mac harddisk connected when doing the following

&lt;pre&gt;
sudo apt-get install hfsprogs
sudo mkdir /media/mac

sudo bash
uuid=$(blkid -t TYPE=hfsplus -sUUID | awk -F'&quot;' '{ print $2 }')
echo &quot;UUID=$uuid /media/mac hfsplus nobootwait,user 0 0&quot; &gt;&gt; /etc/fstab
exit

sudo apt-get install bindfs
mkdir ~/mac
sudo bindfs -u $(id -u) -g $(id -g) /media/mac ~/mac
&lt;/pre&gt;

Once you mount the USB disk through the file mananger, you will have a directory in your home folder called &lt;code&gt;mac&lt;/code&gt; where you can read and write to the USB disk.

The only problem is, that files saved from Linux are saved with user id 1000, where OSX uses 99. So a very hacky way to fix this is

  sudo chown -R 99:99 /media/mac

each time you are done with the harddisk and want to use it on OSX.

[[Category:Mac]]</rev>
        </revisions>
      </page>
      <page pageid="51" ns="0" title="Restrict access to your www pages">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">There are two ways of restricting access to your www pages:[[Image:87-restricted_access.jpg| 500x300px |restricted_access.jpg]]

* user/password requirements
* limit access to specific hosts

A combination of the above is possible as well.

==Password protect your pages==

To password protect a directory tree do the following (assuming your login name is ''nn''):

# Create a directory (e.g. &lt;code&gt;/www/home/nn/public_html/secret&lt;/code&gt;) which are going to be protected
# In that directory put a file named &lt;code&gt;/www/home/nn/public_html/secret/.htaccess&lt;/code&gt;. The content of the file should be something like:
 AuthName &quot;Restricted area - Password required&quot;
 AuthType Basic
 AuthUserFile /www/home/nn/wwwpasswd
 require valid-user

# Next create the passwords:
## Log on to e.g. thinlinc.imm.dtu.dk and type
## Type:
 htpasswd -c /www/home/nn/wwwpassword birger
This will create your personal password file and add user ''birger'' to that file. To add more users you use the htpasswd command again but without the -c option.
# That's it!

'''NB!''' For security reasons you should not put your password file under your ~/public_html directory. Anyhow, the password file must be world readable (i.e. user ''http'' must be able to read it). Also, the passwords have nothing to do with your unix account password (&lt;u&gt;'''and should not have it!'''&lt;/u&gt;). Furthermore, it is not possible to publish documents on the WWW server and preventing other users on the WWW server from accessing it.

To remove a user from the password list, simply edit the password file with a text editor and remove the line with the user of interest.

==Limit access to specific hosts==

To limit access to a directory tree, so only hosts at DTU Compute can access it create a &lt;code&gt;.htaccess&lt;/code&gt; with a content like below, at the moment you need to make entries for both 'imm.dtu.dk' and 'compute.dtu.dk'.

 AuthName &quot;Only IMM clients&quot;
 AuthType Basic
 deny from all
 allow from imm.dtu.dk
 satisfy any

'''Note:'''Many DTU Compute employees/students do not work on a machine that has a DTU Compute address. A more realistic file would be:

 AuthName &quot;Only IMM clients&quot;
 AuthType Basic
 deny from all
 allow from it.dtu.dk
 allow from imm.dtu.dk
 allow from iae.dtu.dk
 allow from ilf.dtu.dk
 satisfy any

This will grant access to all DTU Compute machines plus a few others.

==Combined example==

If you want to allow free access for DTU Compute hosts require a password from hosts outside DTU Compute, the &lt;code&gt;.htaccess&lt;/code&gt; should look like this:

 AuthName &quot;IMM no password - Other needs password&quot;
 AuthType Basic
 deny from all
 allow from imm.dtu.dk
 AuthUserFile /www/home/nn/wwwpasswd
 require valid-user
 satisfy any

[[Category:HC]]
[[Category:Misc]]</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>