On 22 Sep 2017, at 12:12 PM, Yann Ylavic wrote:
> I think:
> ErrorDocument 403 https://somewhere/
> should work.
It does indeed!
https://httpd.apache.org/docs/2.4/mod/core.html#errordocument
Regards,
Graham
—
smime.p7s
Description: S/MIME cryptographic signature
On Fri, Sep 22, 2017 at 12:05 PM, Graham Leggett wrote:
> On 22 Sep 2017, at 12:04 PM, Yann Ylavic wrote:
>
>>> So. I want to be able to send a 302 Temporary Redirect on authz failure,
>>> rather than a 403.
>>
>> Doesn't ErrorDocument work?
>
> I don’t
On 22 Sep 2017, at 12:04 PM, Yann Ylavic wrote:
>> So. I want to be able to send a 302 Temporary Redirect on authz failure,
>> rather than a 403.
>
> Doesn't ErrorDocument work?
I don’t follow, how would ErrorDocument change the response code from 403 to
302?
Regards,
Hi Graham,
On Fri, Sep 22, 2017 at 11:57 AM, Graham Leggett wrote:
>
> So. I want to be able to send a 302 Temporary Redirect on authz failure,
> rather than a 403.
Doesn't ErrorDocument work?
Regards,
Yann.
Hi all,
I am currently struggling with Safari’s behaviour where it re-asks for a user
certificate if the server accepted optional certificates but returned 403
Forbidden. I want the server to send the end user something sensible to explain
what they should do, rather than just have their