Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'no need to pay for a domain name...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
no need to pay for a domain name...
Authored by: algritz on Jul 29, '02 03:14:03PM

If you don't want to pay for a domain name you can simply use your dyndns.org host name in your configuration.

I managed to configure my mac like this and it works fine.

so your email adresse will be

user@hostname.dyndns.org



[ Reply to This | # ]
no need to pay for a domain name...
Authored by: bluehz on Jul 29, '02 05:51:18PM

webDav works fine in stock Mac OS 10.1.5

Anyone know how to create htaccess files (the files that allow/disallow access to web folders, etc) that will allow webdav access to the main folder asking for your login/password, yet allow unfettered (e.g. no login/password) to a subdirectory of the main folder (e.g. sites as in iDisk)?



[ Reply to This | # ]
Don't use .htaccess!
Authored by: Elander on Jul 30, '02 01:56:45AM
Use http.conf instead. A description on how to set up webdav with user authentication can be found on my iDisk. It also tells you how to install webmin to get a more user friendly way of administrating the site.

[ Reply to This | # ]
Don't use .htaccess!
Authored by: bluehz on Aug 01, '02 12:02:31AM

Thx - between your little tut and the link you gave to Apple/SSL instruction I actually got SSL up and running on my web site! Had it installed for a while - just never did anything with it. Matter of fact - the first thing I did was put the SSL to use on my WebMin. Like you - I am a BIG BELIEVER in WebMin - can't live without it. Unfortunately - the last couple of WebMin incarnations have seen some problems with runaway memory. I decide to give the instuction on the WebMin site about running WebMin from Apache a try. Solved ALL my problems AND it gave it a nice little speed boost! In the process though - since you are no longer running the built-in perl miniserver you lose your SSL connection to WebMin. So with your pointers - I managed to secure my WebMin again.

Couple of notes I discovered after several hours of tinkering. I run several name-based virtual servers on my box(es). For those that don't know - see hints on the MacOSXHints site about "virtual hosts". Basically its the ability to have one IP number and host several different named server and have everything directed to the proper location. Unfortunately SSL will not work with name based host - it will only recognize One. There's lots of technical info on why this won't work at both the Apache and mod_ssl sites if you care to dig.

In terms of my original problem - you're technique still does not allow me to offer unfettered (no login/password) access to a subfolder of a webdav-enabled dir. Like this:

/Main-Dir/
/Main-Dir/Pictures/
/Main-Dir/Documents/
/Main-Dir/Sites/

I want any webdav access to take the user to the root level - /Main-Dir/ and require a login/pass. All other access (e.g. http/web) should take the user to the /Main-Dir/Sites/ dir without login/pass and not allow them to traverse back up the dir structure.

At least I have not been able to get it to work - and I tinkered with it all day. Still have not given up yet though.



[ Reply to This | # ]
Don't use .htaccess!
Authored by: Elander on Aug 01, '02 02:29:16AM

You say that you have a structure like this:

/Main-Dir/
/Main-Dir/Pictures/
/Main-Dir/Documents/
/Main-Dir/Sites/

And you want any webdav access to take the user to the root level - /Main-Dir/ and require a login/pass. All other access (e.g. http/web) should take the user to the /Main-Dir/Sites/ dir without login/pass and not allow them to traverse back up the dir structure.

Well, that just won't work. WebDAV uses http, so there is no separation by protocol. The server doesn't treat a webdav client any different from a web browser, and it is not supposed to either. You have to rethink your strategy, i.e. move "/Main-Dir/Sites" somewhere else, or create a separate virtual server.

I would probably do something like this: set up a virtual server on another port (eg 8888), and use webdav to serve up "/Main-Dir/" on that server. Use the default server to serve normal web browsers and use the /Main-Dir/Sites folder as root folder on that.

I haven't tested it, but I can't see any reason why it should'nt work.



[ Reply to This | # ]
Don't use .htaccess!
Authored by: bluehz on Aug 01, '02 02:44:24PM
So far thats the only solution I have found also.
I would probably do something like this: set up a virtual server on another port (eg 8888), and use webdav to serve up "/Main-Dir/" on that server. Use the default server to serve normal web browsers and use the /Main-Dir/Sites folder as root folder on that.


[ Reply to This | # ]