Use Fiddler to see what kind of http code is sent. Most likely it is not 404, but 401 Not Authorized. That explains why 404 Not Found will not apply.
Thanks for the tip Mari. I just used Fiddler to see the response from the server and first I didn't manage to recreate the error I saw before. This time instead of getting the long login URL I got one of our customized error pages but it was not the 404. The server responded with 500 and one of our customized error page was displayed instead. I guess I need to do some debuggin and see what is going on the code. I will post as soon as I get more info.
Did you found the solution. I am also facing same issue.
please let me know if you found anything on this,
I found a problem in an EPiServer instalation. We have a custom "404 Page not Found" page that works fine when trying to surf to a page that does not exist. The problem shows when trying to surf to a recently unpublished page. Instead of being redirected to the 404 page I get redirected to the following page:
The problem just happens for recently unpublished pages. I checked some old unpublished pages and they redirect fine. It is just the pages that were unpublished in the last few days (don't really now exactly for how long they redirect wrong, it could be just some hours to just some days) that do not redirect right.
Any ideas where can I start looking what is wrong or any ideas why is this happening?
Thanks in advance.