Messages in this thread | | | Subject | Re: generalizing khttpd | From | Arjan van de Ven <> | Date | Fri, 11 Jun 1999 20:43:22 +0200 |
| |
> > If there will be a reasonable way to tell the in-kernel server > > from userspace, what set of URLs should be mapped to what files, > > it will be enough to perform this task in fast and secure way, > > leaving all complex work to userspace server.
> Perhaps one could use something based on the way squid currently does > that task.
> 1. If the URL has a ? anywhere within it, squid assumes it to be a > dynamic URL.
If the URL has ? in it, there CANNOT be a file corresponding with it, so this one caught by kHTTPd right now, using the rule "When not servable, do userspace".
> 2. One of squid's configuration parameters specifies a collection of > directory names which, if found in the URL with / on either side > of them, and with at least one element after them, are taken as > indicating that the URL in question is a DYNAMIC one.
Nice idea. I'll think about it.
> 3. Any URL not satisfying one of the above rules is taken to be a > static one.
kHTTPd adds rule 4:
4. If the file is executable or non-world-readable
> ...and rule 2 suggests the use of /proc/sys/khttpd as a file to > specify the directory names to look for in rule 2, with the default > contents being the same as the squid defaults.
Good idea. I'll try to implement it this weekend.
Greetings, Arjan van de Ven
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |