On 2/29/16, Yehuda Katz <yehuda@xxxxxxxxxx> wrote:
> The per-user error log in cPanel - and likely other control panels - is not
> always accurate and you may need to check the main server error log.
So the error that's arising from
<!--#include virtual="/some.html" -->
is the following:
[date][error[client IP] unable to include "/some.html" in parsed
file a.shtml, referer: URL
Again please note this include statement works fine until this [sub]
directory is password protected.
As you're able to make this work at your end I'm thinking either the
commercial server is configured in a way I don't understand, or I'm
overlooking something obvious...
> On Mon, Feb 29, 2016 at 10:22 AM, Dave Shaw <dave.shaw10@xxxxxxxxx> wrote:
>
>> On 2/28/16, Yehuda Katz <yehuda@xxxxxxxxxx> wrote:
>>
>> > What did you do to require passwords?
>>
>> An "AuthUserFile" entry was made in .htaccess for the directory
>> indicating an associated password stored in the .htpasswds file
>> (elsewhere). "AuthType" is listed as "Basic", and another line stating
>> "require valid-user".
>>
>> > On Feb 28, 2016 12:35 PM, "Dave Shaw" <dave.shaw10@xxxxxxxxx> wrote:
>> >
>> >> Greetings-- We're setting up a website on a commercially-hosted server
>> >> that supports SSI. The website includes a number of sub-directories.
>> >> In a 1st-level subdirectory we have some html that includes similar
>> >> to:
>> >> <!--#include virtual="../some.html" -->
>> >> and
>> >> <!--#include virtual="/some.html" -->
>> >> All this has been working fine.
>> >>
>> >> We now want to password protect access to one of these directories,
>> >> and when we do, password protection works fine, but the SSI statements
>> >> fail with:
>> >> [an error occurred while processing this directive]
>> >>
>> >> I've dug around in the documentation and haven't found any
>> >> restrictions on use of SSI in password-protected directories, but it's
>> >> acting like password protection might be doing a "chroot" to that
>> >> directory or something similar. Is this an option in the server
>> >> configuration?
>> >>
>> >> If you can help explain this I'd be appreciative.
>> >>
>> >> Dave
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>> >> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|