[gopher] Whole lotta hits

[Kim Holviala]

On 15.9.2011 17:46, Jacob Dahl Pind wrote:

>> I was thinking about Apache-like Allow/Deny directives, but those
>> would have required a config file instead of just simple options.
>>
> if they where like .htaccess they would have to be in the directories,
> and first be read at the access of them, just like the gophermap in menu.c.

What are you, a mind reader? Stop it.

OUT OF MY HEAD! Need. Tinfoil. now.

>> At the same time I was also thinking about doing password-protected
>> directories. Easy enough to do even with the original protocol, but
>> I'm not sure if anyone would find those useful...
>
> Well protected directories could be done through scripting, search
> selector and executeable gophermap files, think it would be easier to
> implement it that way.

The problem with scritable password-protected directories is 
deeplinking. Say you want to protect 1/dir/ - that's easy enough with an 
executable gophermap. But how do you prevent deeplinks to 
0/dir/file.txt? Some clever symlinking would work, but it gets really 
messy...

Integrating passwords into the session system would be easy and would 
also prevent deeplinked resources from being available without the 
correct password.



- Kim