IP Filtering and Page Not Found package

[tekoscott]

Feature summary

Hi Nik

Not sure if this is a feature request or a bug.

I have IP filtering set up in the web config of a Umbraco 13.5.2 site. The aim of this is to prevent unauthorized access to the umbraco backoffice. We do not want the public to even see the backoffice login page, we only want vpn access to the backoffice.

I think that the ip filtering, because it is in the webconfig occurs first in the pipeline before your package is loaded and configured in the pipeline.

The package works perfectly as expected except when trying to call the /umbraco directory. It then presents a generic .net style 404 page.

I hope this make sense I can clarify further if required.

Additional details

No response

[NikRimington]

Ohh, interesting idea.

Yeah currently this wouldn't be possible with the Page Not Found Manager as it's using the Umbraco Content Routing pipeline.
If you used your IP block for the Umbraco back office to redirect to "/not-found" or something like that it would be a work around.

Alternatively you could use a "rewrite" as opposed to a redirect, so it masks it a bit more.

That might help you out, but I'm not sure how PNFM could be modified to do this for you.

[tekoscott]

No worries Nik,

I can work around it I basically needed to confirm my hypothesis.

Thanks for looking into it.

Excellent package by the way.