Again new old problems, also with Joomla

MIB

Hello dear people,
I had this topic here a long time ago, but unfortunately it was not really resolved.
I want a 301 if ...
* NOT mail.mydomain.de
- OR
* IS any other.mydomain.de
The fact that it does not redirect at "mail.mydomain.de" seems to work (HOST not equal to "mail"). But what is missing here is "is equal", so that I could write "HOST is equal to www". That would actually be the end of the matter. But that's simply missing.
* Question: How can I redirect a request from "www.mydomain.de" to "mydomain.de" by other means?
Another topic in this context:
I'm currently trying to get the latest Joomla version up and running, including rewriting the URLs to readable URLs. In addition, Joomla provides an htaccess in which everything is regulated. But Abyss simply ignores them ...
* So the question about this is how you can make this thing work?

admin

M*I*B,
The human way of explaining things can sometimes make it difficult to translate it to the machine context:
Do you confirm that you want to do a 301 redirect if
HTTP_HOST not equal to mail.example.com
AND
HTTP_HOST matches with *.example.com
?
Regarding Joomla and their htaccess file:
htaccess files are only for Apache. So you have to convert their URL rewriting rules or ask us for help (just send us the file and we'll convert it for you.)
Conversion rules are outlined in https://aprelium.com/abyssws/articles/urlrewriting-modrewrite-conversion.html but most of the time htaccess files are overengineed and we could simplify them to a single URL rewriting rule or two.

MIB

hmmm... like that... With other words:
I have 4 domains. Let's call them D0 (master) to D3.
I have a webmailer which can be called up under mail.Dx. This is the only subdomain that is allowed.
The call of any domain with the WWW or something else than mail in front of it should redirect to D0 (301 permanent), as well as the call of D1-D3 without anything in front of it.
So...
http (s)://D0/* is the Master destination
http (s)://mail.Dx -> https://mail.D0
http (s)://[NOT mail].Dx/* -> https://D0/*
In the meantime I have done the following, which seems to work at first:
Rule 1:
^/(.*)$
HTTPS Is not equal to ON
HOST Is not equal to mail
Apply to subrequest
Perform external
Redirect to https://D0/$1
Append Query
Escape Redirection
301
Rule 2:
^/(.*)$
HTTP Header: HOST Does not match with ^D0(.*)
Apply to subrequest
Perform external
Redirect to https://D0/$1
Append Query
Escape Redirection
301

admin

M*I*B wrote
hmmm... like that... With other words:
I have 4 domains. Let's call them D0 (master) to D3.
I have a webmailer which can be called up under mail.Dx. This is the only subdomain that is allowed.
The call of any domain with the WWW or something else than mail in front of it should redirect to D0 (301 permanent), as well as the call of D1-D3 without anything in front of it.
So...
http (s)://D0/* is the Master destination
http (s)://mail.Dx -> https://mail.D0
http (s)://[NOT mail].Dx/* -> https://D0/*

The requirements seem to change from day to day. :) Are you sure this is the final version?
How many hosts do you have? How are these domain names associated with the hosts (D0, mail.Dx, *.Dx)?
This will help us give you a way to write these rules without loops or ambiguities.

MIB

... nope, it's ever the same domains ;o) Trust me ...
I just have write it down in different ways due I think that we most not talking about the same ...
D0 = Masterdomain
D1 = Slave 1
D2 = Slave 2
D3 = Slave 3
Dx = Any of them above (x = 0 or 1 or 2 or 3)

admin

M*I*B wrote
... nope, it's ever the same domains ;o) Trust me ...
I just have write it down in different ways due I think that we most not talking about the same ...
D0 = Masterdomain
D1 = Slave 1
D2 = Slave 2
D3 = Slave 3
Dx = Any of them above (x = 0 or 1 or 2 or 3)

We understood all about the domain names. But our question was about the hosts. How many hosts do you have? (H1, H2....)
Which domains are associated with which hosts? (for example H1 -> D0, H2->D1,D2 ...)
We need the mapping with hosts and domain names to know what to configure and how rules should be after resolving domain names.

MIB

ahhh ok ... Now I get it ...
Just 1 Host where all the Domains are in ...

admin

M*I*B wrote
ahhh ok ... Now I get it ...
Just 1 Host where all the Domains are in ...

So we'll assume you have a first host associated with host names D0, D1, D2, D3, *.Dx. This host should have the following URL rewriting rules:

Rule 1: 
^/(.*)$ 
HTTPS Is not equal to ON 
HOST does not match with mail\.(.*)|D0

Apply to subrequest 
Perform external 
Redirect to https://D0/$1 
Append Query 
Escape Redirection 
301

The second host will be only associated with host name mail.D0.

MIB

... sorry for late reply; was sick a while ...
Ok. that doesn't work.
www.D0.de dont will be rewritten to D0.de, also www.Dx.eu stay at it, also mail.D0.eu stay at eu and will not be rewritten to de.
This rule simply does ... nothing.
I think it won't work, especially not with regard to the second part "Joomla" ...

admin

M*I*B wrote
... sorry for late reply; was sick a while ...
Ok. that doesn't work.
www.D0.de dont will be rewritten to D0.de, also www.Dx.eu stay at it, also mail.D0.eu stay at eu and will not be rewritten to de.
This rule simply does ... nothing.
I think it won't work, especially not with regard to the second part "Joomla" ...

Could you please send by email to our technical support your abyss.conf file for review?

MIB

... no longer necessary: I'm back to Apache on this server

admin

M*I*B wrote
... no longer necessary: I'm back to Apache on this server

Apache doesn't have AI to auto-write URL rewriting rules. :) So how have you solved the issue with it? What made Apache so superior in that use case?
Can you show us the redirection rules in your .htaccess?

MIB

... Unfortunately you did not understand it, but I will explain it again:
Joomla and other systems almost always have their own htaccess file. Abyss cannot read this htaccess. So there is a need to translate this htaccess into the Abyss format.
That's why I asked for help here. And that wasn't the first time I've asked for help with things like this, which was mostly unsuccessful.
With Apache I didn't need to ask anyone for help, since Apache can natively read and implement the htaccess from e.g. Joomla. In addition, there are so many pages on the topic of Apache, htaccess and mod_rewrite that I can usually help myself there.
Finally, I would like to say the following:
At the time I bought Abyss because I was tired of having to manually renew the certificates because there was nothing useful for Apache under Windows. In the meantime, that has changed.
I also found that Abyss causes problems with many other things, such as when you just want to run a simple update under WoltLab. There is also a thread from me here that ultimately had no solution to the result.
Nothing against Abyss. For some users this is certainly quite sufficient. In the meantime, however, I was able to determine that Abyss caused me significantly more problems than Apache, which also were and are not solvable.
Conclusion for me:
I will probably continue to use Abyss for some small applications on my test server. For my live systems, however, Apache is and remains the first and only choice.

admin

M*I*B,
Most mod_rewrite directives in Joomla and similar scripts boil down to the same set of URL rewriting rules. There is no magic there.
What you were asking about above had nothing to do with Joomla or its URL rewriting rules.
You were asking for a complex scheme of redirecting a set of domain names to another one based on complex rules that you were changing on each clarification request from us: Joomla doesn't deal with things such as:

http (s)://D0/* is the Master destination 
http (s)://mail.Dx -> https://mail.D0 
http (s)://[NOT mail].Dx/* -> https://D0/*

Anyway, we hope your switch made things easier on your side. We are also sure you'll come back to Abyss after a while :)

MIB

You are right. This last things are not Joomla but there is a thread about that.
And also this thing here is easy to handle by Apache without rewrite just by placing a Redirect 301 directive to every vHost you like to redirect...
Sample:

<VirtualHost *:80>
	...
	ServerName master.de
	...
</VirtualHost>
<VirtualHost *:80>
	...
	ServerAlias slave1.eu
	ServerAlias slave2.de
	ServerAlias slave3.eu
	ServerAlias www.master.de
	ServerAlias www.slave1.eu
	ServerAlias www.slave2.de
	ServerAlias www.slave3.eu
	...
	Redirect 301 / http://master.de
</VirtualHost>

That's it. Webmail, other special subs and SSL (just place the Master in the AliasVH and Redirect to httpsVH declared in the 1st VH) follow the same schema you can handle without the need of rewrite-rules

admin

M*I*B wrote
That's it. Webmail, other special subs and SSL (just place the Master in the AliasVH and Redirect to httpsVH declared in the 1st VH) follow the same schema you can handle without the need of rewrite-rules

And you could achieve the same thing with Abyss Web Server by creating a first host master.de and a second host which has all these names then add a single rewriting rule as follows:

Rule 1: 
^/(.*)$ 

Apply to subrequest 
Perform external 
Redirect to http://master.de/$1 
Append Query 
Escape Redirection 
301

But keep in mind that you Apache except does not handle HTTPS and some use cases you raised. So it's not equivalent to the original quiz.