From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Alexey Borzov" <borz_off(at)cs(dot)msu(dot)su> |
Cc: | "PostgreSQL WWW Mailing List" <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: New site - mirroring issues |
Date: | 2004-12-16 13:33:20 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4527F40@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
> -----Original Message-----
> From: Alexey Borzov [mailto:borz_off(at)cs(dot)msu(dot)su]
> Sent: 16 December 2004 13:20
> To: Dave Page
> Cc: PostgreSQL WWW Mailing List
> Subject: Re: [pgsql-www] New site - mirroring issues
>
> OK, don't see anything obviously wrong with the links. I'll
> probably try
> running the mirroring script myself tomorrow to understand
> the source of
> this problem.
OK, thanks.
> Once again: you can't have both foo.html and directory foo/
> on a static
> mirror. Therefore you need only to get directory foo/ and an
> index.html
> file within it. To achieve this, you *only* need to change links on
> dynamic website from foo to foo/. You don't need to touch or
> rename the
> foo.html template itself.
Ahh, yes - that got it - thanks. On further investigation I realised
that other similar files/directories were unnaffected - the difference
being that for /about/ for example, we had
about/
about.html
about/index.html
With the latter being the file that was actually served. With
about/casestudies, the index.html was missing.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2004-12-16 14:06:37 | Re: New site - final(?) list of problems |
Previous Message | Alexey Borzov | 2004-12-16 13:20:10 | Re: New site - mirroring issues |