php@xxxxxxxxxxxx <mailto:php@xxxxxxxxxxxx> wrote:
> I run several intranet sites for our company on a linux
> server using VirtualHosts. I've created a wildcard SSL
> certificate for our intranet sites which work when I browse
> to the fully qualified domain name (i.e.
> https://home.domain.org) but most of our users use the short
> name to get around (https://home) which causes a security
> warning. Is there a way to fix this or am I doomed to
> require users to use the fully qualified domain name?
Perhaps you can use a rewrite rule to point the to the FQDN.
http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewritecond
This may or may not work for you; I'm not exactly a rewrite-guru, but
*something* along these lines is what I'm using to do some rewriting
(and this is my only experience with it):
<Directory ...>
RewriteEngine on
RewriteCond %{SERVER_NAME} !^<Your_FQDN>$
RewriteRule ^.*$ https://<Your_FQDN>%{REQUEST_URI} [L,R]
...
</Directory>
Grts,
Rob
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|