In a non-directory context, just anchor your target, and you can skip the
RewriteBase altogether.
Redirect requires two parameters in the vhost/server context.
On Wed, May 3, 2023 at 6:57 PM Jim Weill wrote:
> On Wed, May 3, 2023 at 3:45 PM Frank Gingras wrote:
>
>> 1) Avoid rewriting from
On Wed, May 3, 2023 at 3:45 PM Frank Gingras wrote:
> 1) Avoid rewriting from or blocks.
>
RewriteBase says it cannot be called outside , is that not the
case...?
> 2) Avoid using mod_alias (redirect) from that context as well
>
I tried putting the redirect outside the and it would not
1) Avoid rewriting from or blocks.
2) Avoid using mod_alias (redirect) from that context as well
3) Provide more than one rewrite log line, context matters
4) This can be replaced with FallbackResource /index.php:
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
The logs say something of the form: input=full.website.base.URL
pattern=hostname.fq.dn not matched
Where am I going wrong here?
jim
On Wed, May 3, 2023 at 9:55 AM Jim Weill wrote:
> We have a website that has been in use for a project for years, which
> someone else took up and would like
We have a website that has been in use for a project for years, which
someone else took up and would like the site permanently redirected to the
new URL. For whatever reason I cannot get this redirect to work
consistently, and I'd like to know where I'm going wrong.
The only thing I changed on
Nothing that I could find in the documentation says that the OCSP stapling
does anything outside of that. The OCSP server will add that status to the
handshake / response. I guess is there a way to check that OCSP response
status in Apache and manually block this based on it?
