Can I redirect this:
http://example.com:2095/logout/?locale=es
To
http://subdomain.example.com
It's to customize the log-out page of a webmail. Have no root access.
The logout link comes from the cpanel webmail logout.
Typing the same logout URL in the browser, or getting logout by webmail link takes to the same logout page (no results in redirecting with .htaccess). (Other URL redirects works fine)
Hostgator support didn't give any concrete info about redirecting from ports 2095 or 2096. Basically I was told that they're are used for webmail and I should not be trying to customize anything about it.
Related
I have a Perch web site which will be moving (gradually) to a new domain, so I need to redirect some pages to the new URL.
e.g. mysite.com/page1 => mynewsite.com,
mysite.com/page2 stays the same
I have tried doing redirects using .htaccess, for example:
Redirect 302 /page1 https://mynewsite.com
This works fine if you type the URL in the browser address bar, but when I click on any link to page1 on the web site, all I get is a white screen and no redirection (I have cleared the browser cache). But then if I refresh the page, it redirects. What am I missing, is there a specific way to redirect Perch pages using .htaccess?
I can't see any way to add a link manually in the admin section (sorry I am not very familiar with Perch) - all I can see is 'Page to link to', with no option to enter an external link. How can you set the link to an external URL?
Thanks.
I am unable to login to the Opencart Dashboard. I can see the login screen and enter passwords. I even did a fresh install. It just doesn't redirect me to the dashboard. I have read up and tried every possible solution. Is there something on the server that could be blocking the re-direct.
This could be caused by .htaccess redirect. It happened to me too because my website was getting redirected to www.example.com but the session was for example.com. Make sure you have the same version of the url everywhere.
I used the method described at: Mobile Redirect using htaccess to redirect mobile. Works great.
Now, what my client is trying to do is if someone is on mobile, if they are trying to access that is not the homepage, then they do NOT get redirected. So, if they ARE opening the homepage, the redirect works as normal. If, for example, they are opening anything else such as the blog, it does not redirect to the mobile site. So, the only time they get redirected is if they are trying to access the homepage.
For some reasons Google custom search result shows https:// for some of my page links. The only solution for now would be to redirect the https:// links to http:// with htaccess for now until i figure out why search results are showing https://
I want the redirect to bypass the SSL cretificate or "Add Exception" page and redirect to http://
You won't be be able to do this with .htaccess because for the client to get the redirect it will have to have already started the SSL session (and therefore shown the add exception page) The only way around this is to buy a real certificate signed by a trusted CA.
You could also sign up for Cloudflare HTTPS. They offer it free of charge right now. You can then enable SSL on the entire site, and redirect to HTTP, or HTTPS. Your choice. This would prevent the warning from being issued.
I'm the IIS admin, not the developer on this site, so the code is opaque to me. I'm stumped, though, for where to look.
Using Windows Forms Authentication, the user is directed to a login page. If their password is expired, they are directed to ChgExpiredPwd.aspx. On our dev and test servers this works. On our production server, the user is redirected to login page again with a "ReturnURL=ChgExpiredPwd.aspx". Not the desired behaviour.
Fiddler says the server is responding with an immediate 302 redirect to the login page. The test server responds with a 200. The IIS properties for the site and for that page have no redirects - all, "The designated file." There's no redirect built into the codebehind so's I can see it. No redirects in the target page, though the redirect is happening server-side, so it has to be in the code somewhere. If I take \bin*.dll from production and put it all on test, it does not reproduce the error.
I'm out of ideas.
Have a look in the web.config file at the root of the site. Forms based authentication is typically configured there and the default behavior is to redirect from a "secure" page to the login to authenticate (if the user has not yet done so), and one of the parameters it passes is the ReturnURL.
This explains it pretty well: http://msdn.microsoft.com/en-us/library/aa480476.aspx