You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the expected output?
To be able to permanently redirect (301) the server's address to a different
page on a different server.
What version of the product are you using? On what operating system?
Mongoose DEV 5.4.2 on Windows Server 2008 R2 Datacenter
Please provide any additional information below.
I would like to redirect the page to another page in a different server. I have
purchased and installed Mongoose because of its very low footprint on the
server. I am currently using the re_write option using the errors 403 and 404
to temporarily move the page to the correct destination,since I have no data
what so ever on the shared Web folder on the server that Mongoose is installed.
But when Mongoose redirects it to the real website, it shows the parameters on
the address bar, which is not the ideal solution whatsoever. The ideal solution
would be a field to insert the address for a permanent 301 redirection.
Thank you very much for your help.
Kind regards,
Giovanni
Original issue reported on code.google.com by [email protected] on 22 Oct 2014 at 2:35
The text was updated successfully, but these errors were encountered:
Giovanni, Thank you for your request. But its nature indicates that you may not
understand the purpose of Mongoose. It is not meant to be a replacement for
Apache, and is not meant to be a general-purpose Web server. If we added all
useful Apache directives, Mongoose would no longer be tiny!
It is a tiny server meant to be part of a stand-alone application. In this
usage, the data for the application is present on the same site. Redirection is
not needed.
Even if data is in a different domain, it can be fetched through Mongoose (for
example, using PHP, which is almost fully supported) without top-level
redirection.
For example, suppose we want to put some Web pages on a CD, and hand them to
customers. If we want the CD to serve those pages, as though it were a website,
we can accomplish that by using Mongoose.
Unless you can give a use case (an example of usage) for the proposed feature,
it is unlikely to be accepted.
Original issue reported on code.google.com by
[email protected]
on 22 Oct 2014 at 2:35The text was updated successfully, but these errors were encountered: