If you have SSH connectivity, you can do it quite easily from the command line.... it only takes creating a separate virtual host file and you are ready to go...
If you are up to it, I can give you some examples.....
The improved apache conf unfortunately still suffers from the global alias problem, which makes it necessary to force virtual hosts to return 404 on any defined virtual host.
The improved apache conf unfortunately still suffers from the global alias problem, which makes it necessary to force virtual hosts to return 404 on any defined virtual host. like virtual host : http://www.mywebsite.com/somedir/admin will ask nas credientials and will login into the admin interface of the nas....
Since the configs mdgm pointed to don't use any global alias definitions at all I wonder why you are running into this problem. The only possibility I can think of right now is that you include DefAlias.conf somewhere in your new virtual host. Any chance I can have a look at your configs?
Just to clarify, I am currently not using the new config files...
I just glanced over them and saw the global aliases in DefAlias.conf (line 88 for instance in x86)..... so I am just assuming as I am not an apache conf specialist, I am merely extending my experience with the standard readynas apache. I could be wrong of course...
I, in fact, would be very happy to see the global aliases disappear...
Just to clarify, I am currently not using the new config files... I just glanced over them and saw the global aliases in DefAlias.conf (line 88 for instance in x86).....
Yeah, thanks for having me chase a non-existent bug 😉 Of course there need to be Alias definitions for Frontview to work properly. But since they are included in a VirtualHost context they don't affect other VHosts. With the config layout I posted even the add-on are no longer global but locked into the default VHost. Now if you are going to include the DefAlias.conf within another VHost context you'll of course again have the same problems as usual. But I don't see why one should want to do that 😄
A good scare once in a while keeps the bloodstream free of obstructions... so actually I contributed to your health...
Well, this places me in a awkward position to try the new config and give first hand experience comments rather than 'think so' ones. Before I completely ruin my apache config, how stable is this when a new firmware is installed ?
Since a new firmware always overwrites the Apache config files I'd say it's exactly as stable as your manually edited config 😉 That said I'm working on a method of detecting an overwritten config and restoring the changes but that's not finished yet. But since the project is on Gitorious and since Gitorious is free, feel free to improve my version and send me merge requests 😉
ok, let me try the new config an I get back to you...
Concerning submitting merge requests, I fear my apache config skills are not better than copying and slightly adapting examples I find on the internet.. It took me literally weeks to get authentication against a readynas user... but using one of your examples of the kmotion addon I managed...
