Forum Moderators: open
I currently have a blog engine running on IIS and ASP, available to our readers and it works (it does) like this:
- reader enters [[mydomain]...] or [[mydomain]...]
- the non-existant folder [username] is caught by 404.asp which validates the user name, and if a blog is active it does a response.execute blog.asp with some session parameters, including blog post id (if entered).
This is greate because it preserves the URL entered by the user, while processing 404.asp and blog.asp. It also works with SE because the original URL is the one seem by everyone, include bots. And our internal links are in this format.
Now to the questions:
- Sometimes in the odd occasion, instead of preserving the URL, it actually shows the 404.asp redirection in the address bar, as in [[mydomain]...] exactly what the IIS would pass to the custom error page. This happens only if coming from a link in another program, such as MSN Messenger or Microsoft Outlook. It happens on any browser, Mac or Windows. Ideas?
- The most important one: a few users have their own domains available. They would like to have [[userdomain]...] being processed by [[mydomain]...] but keeping the [userdomain] in the address bar. The domain IP would point to our server, so it would be in the same machine as the blog engine.
I haven't test it yet, but I don't think IIS would execute a script from another domain. Or will it? Did anyone come across this scenario?
Thanks in advance
