Why does a Non-existant page returns 302 status when using a custom 404 page in asp.net -

I have set up a custom 404 page custom 404.aspx that returns the "404 Not Found" error properly, though The non-existent page which initially requested was given "302 found" status.

So when I test this pageodocortexist. Aspx, it returns "302" then returns a custom 404.aspx and returns a "404 Not Found" status.

I want to make sure that search spiders / bots understand that the requested page is not present and should not appear in any search results. Is this setup properly?

To answer the question asked, it is fine how a custom error works in ASP. met. I have seen an example (although I do not have one thing) where people have used the HTTP module to block errors, and serve users a custom error page that does not look like a finger, and users For 404 response bot.

In a different direction, I'm not sure that the bots follow 302 responses regularly. Perhaps more relevant, is it true that your error page (it is useful to believe) is shown in search results? At least the user has a link to your site - which is better than showing your competitor site ...