[BlueOnyx:24238] Re: Personal web pages in 5210R

[Meaulnes Legler @ MailList]

On 31.08.20 00:57, Ernie wrote:
> Very interesting.
> I will have to study up on the AliasMatch function, looks like it might solve
> my problem
you're welcome!

> The 5210R has a different directory structure to the 5109R, so you will have to modify your
> rules. I am still tackling the auto addition of subdomains for 100+ users
> where the DNS is on another server.
> - Ernie.

please let me know what you could find out, I'm very interested for that setup for my future 5210Rs...

Best regards

で⊃ Meaulnes Legler
Zurich, Switzerland
+41¦0 44 260-1660
bluelist at waveweb.ch


> 
> 
>> hello
>>
>> I also run 5209Rs (looking forward to upgrade to 5210R!:-) and also used a similar «rigging» that Michael proposed.
>>
>> For many users, specially those with foreign keyboards, the use of the ~ tilde is too intricate and/or they aren't able to type it... So I added this line in httpd.conf (actually in /etc/httpd/conf/vhosts/site#.include where # is the site number) so one could use a - hyphen instead of a ~ tilde to open its personal web:
>>
>> AliasMatch ^/~([^/]+)(/(.*))? /home/.sites/###/site#/users/$1/web/$3
>> AliasMatch ^/-([^/]+)(/(.*))? /home./sites/###/site#/users/$1/web/$3
>>
>> That works fine. But unfortunately the redirection to the subdomain from name/domain/tld to domain.tld/~name didn't work, maybe because of recent https installation. Hopefully with 5210R?
>>
>> Best regards
>>
>> で⊃ Meaulnes Legler
>> Zurich, Switzerland
>> +41¦0 44 260-1660
>>
>>
>> On 28.08.20 20:58, Michael Stauber wrote:
>>> Hi Ernie,
>>>
>>>> so how do I intercept the http://FQDN/~username requests, and force them to
>>>> redirect to a subdomain?
>>>
>>> A mod_rewrite rule could do that. On 5209R and older the following rule
>>> redirecs <domain.tld>/~username to where it needs to go:
>>>
>>> AliasMatch ^/~([^/]+)(/(.*))? /home/.sites/75/site8/users/$1/web/$3
>>>
>>> So $1 is the username and $3 the file name (if any). Based on that I'd
>>> say something like this might work:
>>>
>>> RewriteCond %{REQUEST_URI} ^/~([^/]+)(/(.*))? [NC]
>>> RewriteRule (.*) http://$1\.example\.com/$3 [R=301,L]
>>>
>>
>>
>> _______________________________________________
>> Blueonyx mailing list
>> Blueonyx at mail.blueonyx.it
>> http://mail.blueonyx.it/mailman/listinfo/blueonyx
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx
>