i have a really weird problem on a typo3 site.
The site currently runs on Typo3 4.6.6 (yeah i know we are in the process of upgrading it to 6.2 LTS)
In the backend we have 3 separate pages. The webspace where this site runs was currently upgraded to PHP 5.5. Nothing else has changed (as far as we know)
The problem is that on certain pages we get redirected to a https version of the same page, although the link is a http link.
See for instance here: http://www.phd-cell-signaling.at/home.html
If you open this it loads fine. But as soon as you click on a (http) link on the site, you get redirected to an https version hence the browser doesn't load all the stuff included via http (stylesheets for instance). But when you then delete the "s" from the address bar and hit enter you don't get redirected. And this is something i don't really understand.
And if that'd be a general issue shouldn't the other pages in the same typo3 environment also be affected? Or am i missing something here.
Since I'm not that familiar with typo3 it would be greatly appreciated if somebody could link me in the right direction where the problem could be.
We use realURL for example. But I checked the configuration i found and it doesn't appear to do anything that causes the redirect.
I also checked the typoscript configuration of all the pages in the backend with no success.
Are there any other plugins that might cause something like this?
Any help greatly appreciated.
When you follow a link on the page you posted, then the webserver returns the statuscode 301 (moved permanently) with the new location for that page (which is the requested page with the HTTPS scheme).
When TYPO3 is properly configured for SSL usage for single pages (so a backend user can use "Choose protocol" selectbox in the backend), then it already renders affected links with the proper scheme.
Your problem described can have multiple reasons. Please check the following:
Inspect the .htaccess file in the root directory of the TYPO3 website for any scheme redirects
Check if the webserver itself has configured scheme redirects for that virtual host
Goto the TYPO3 extension manager and search for local installed HTTPS or SSL redirection extensions
Related
I have purchase and installed an SSL certificate on my server and everything seems to be working correctly.
I selected in Joomla Global Configuration -> Server -> Force HTTPS -> Entire Site. Now the site all works with SSL as expected.
But, I have 2 pages that needs to be in http because the remote call does not support https :(
I have been fiddling with joomla native .htaccess but I either get redirection loops or errors.
Could someone please help with the correct .htaccess code for force http in 2 pages?
There is a component that can be used to enable https on specific pages of website only. Check this https://extensions.joomla.org/extensions/extension/site-management/url-redirection/yireo-ssl-redirection/.
This will make your work easy no htaccess required.
I have working Drupal project on an old server running Apache2. I am trying to move to new server running nginx+php-fpm. I also changed the site's domain during the move.
The move was mostly successful except a few details:
In the admin panel #overlay stoped working and every link (ex.: mysitename.org/#overlay=home/structure) rewriting to mysitename.org/home/structure. I guess I have some problems with new php.ini/nginx rewrite rules or something similar but cant find out what exactly.
After login user being redirected to mysitename.org/users/username but on previous domain user stays on page he was logging. Database and files of Drupal are exactly the same on both servers.
image_captcha module stops generating visible captches. Have read many topics about this module but no answer found. (GD JPEG support is ON)
I am really new to Drupal and playing around with this existing Drupal site.
I did a FTP transfer of all the files to my local computer directory. I currently got it on a Vagrant box and I can access the site via http://192.168.56.101/html.
I can do http://192.168.56.101/html/anything-but-user and it brings me to the proper area on the site. However I can't do localhost/html/user, because it redirects me to the website URL rather than the local URL.
I tried clearing the cache (with Drush). I scanned all files in the system and changed the web url to the local URL [not sure if I need to do any other command], and I can't seem to find anything in the .htaccess files that would lead me to this.
The href="/user I would greatly appreciate any advice or help in figuring out this solution.
--UPDATED
There was a module called "Secure Pages" that was causing the user and registration links to be locked and static to prevent redirects to phishing sites. I had to disable this module using "drush pm-disable securepages" in the terminal.
Some typical items you may want to check:
Check if you get the same problem using another browser. If with another browser it works, then it is pretty sure a cookie problem. To solve that, delete the cookie in the browser where you have the problem.
Make sure "clean urls" is enabled. Refer to "https://drupal.stackexchange.com/questions/165029/clean-url-leads-to-duplicate-url-after-migration-to-another-hosting/165044?s=1%7C3.9647#165044" for more details on that.
Make sure the value of "base_url" is set correctly (in your settings.php).
If module Secure Pages is enabled, then try to (at least temporary) disable that moduel to see if it helps.
Apparently, there was a mod called "SecurePages" that was causing the URLs to be static to prevent someone from changing them and redirecting users to a phishing site.
I'm having some trouble with a drupal page. The website is loading and nothing is out of the ordinarty. But when you load the page with Google Chrome development shizzle (when you press F12) and put it on Network and then reload the page, you see that the first thing that happens is receive an 404 error.
It's not that big of a deal but our monitoring system says the website is offline because of this.
Does anyone knows what is going on? I have absolutely no idea why this is happening.
I'm running into this exact problem with a D7 site on a new server that has PHP 5.5.9 installed - the page loads but the HTTP header says "HTTP/1.1 404 Not Found" for all pages but the homepage. If I work out a solution I'll post it here.
Update: It turned out my problem was that mod_rewrite was not enabled, once I enabled it the site started working correctly.
Drupal allows customizing 404-403 error pages. Probably, your site (by some reason) displays content on 403/404 pages.
At first, clear cache (using web ui or drush).
This can be 1-page issue (check /user/login, admin pages, node pages). Maybe, only your front page is not found.
If this is not 1-page issue, check and disable customerror module (if you has one installed).
I am developing a website in php.
when a user types a page which is not in my site, i want users to redirect to a page with an error message.
how can i identify such things and how can i do this??
Thanks.
If you're using Apache web server, you get this functionality for free. No need to implement it yourself. If the web server cannot find an resource it sends the client an HTTP 404 error (not found). Actually, pretty much any web server that correctly implements HTTP (1.0 or 1.1) will behave this way. Additionally, in Apache, you can customize the 404 page.
If you're using Apache, here's instructions:
http://www.thesitewizard.com/archive/custom404.shtml
This is not really a php feature, but more of a feature of your web server. In IIS you can configure the error page to go to a custom url. In apache i think you can usr mod_rewrite to achieve the same thing
Other than what others said this might be of some help too "Custom 404 Error" if you are using Apache.
If some script is launched on all of your pages (it can me unit, which is always included) you can make a check there. You should write there all of your available pages and if the required page is not in the list - you can show person, that he/she was wrong.
Sometimes the list of pages is jept in database. Most CMS-systems are based on that.