Allow/Deny by realm
Brought to you by:
cshotton
It would be great if the support for HOSTFOLDER allowed
to specify ALLOW/DENY for a specific HOST. From top of
my head, I imagine it would be easiest to add
HOSTFOLDERALLOW intranet.myCompany.com 123.45.6
HOSTFOLDERDENY intranet.myCompany.com 123.45.6.7
So the normal ALLOW and DENY are used at the entry point
(as they are now) and these are triggered only when a
specific HOSTFOLDER is detected in the URL.
The reason for this should be obvious: it would allow us
to run public and private sites using a single copy of
MacHTTP.
Logged In: YES
user_id=381409
Logged In: YES
user_id=381409
An alternative could be to implement a more generic
FOLDERALLOW folderpath 123.5.6
FOLDERDENY folderpath 124.5.6.2
This would give even greater flexibility and make this
feature independent from HOSTFOLDER which may or may not make
the implementation easier.
Logged In: YES
user_id=6221
This will be implemented when Allow/Deny by realm is
functional in a post-2.5 release. You will be able to
have any path matching a specific realm string be
subject to specific allow/deny commands.