Let's say I have a website - example.com. If I create a binding in IIS, with *.example.com then abc.example.com works.
However, abc.in.example.com doesn't work. It gives me 404 status code.
Any suggestions.
-
1Is: "Learn how wildcards work" a valid answer for you? Because you expect things to work that are explicitly not working by standards.– TomTomJan 23 at 9:55
-
@TomTom Not sure. If one only knew how it worked, there wouldn't be this question.– TusharJan 24 at 8:34
-
Yeah, but rtfm is not really optional. It is clear in any documentation i ever read that wildcards are ONE LEVEL ONLY and do not extend downwards.– TomTomJan 24 at 9:30
Add a comment
|
1 Answer
This is how wildcard certificates work. *.example.com work only for hosts like: host1.example.com, host2.example.com, etc.
If you want to have it work for abc.in.example.com you need to use certificate for *.in.example.com
The same is situation with binding to wildcard hosts.
-
1
-
@Tushar, if you are happy with my answer feel free to accept it (tick on the left side of the answer) :) Jan 24 at 9:05