I have a TYPO3 site now running under https. All works fine, except for clicking on Show on a page in the Page tree. I then get an invalid URL which starts like 'https://https//www.'
Steps I did:
Domain record bla.com 301 redirect to https://www.bla.com
Domain record https://www.bla.com
Force SSL backend via $GLOBALS['TYPO3_CONF_VARS']['BE']['lockSSL'] = 2;
Should I set something else to have correct 'Show' links from the pagetree?
thanks
Do you use the backend over SSL too? Died you try to set the url schema inside each page settings from http:// to https:// to exclude this as the error?
In tsconfig TCAdefaults.pages.url_scheme = 2 needs to be added (I already had that, but thank you Paul). But a domain record was wrong; the 2nd one needed to be entered without https://
Related
Hope that someone can help me solve this strange https:// behaviour in TYPO3 8.7.2 (and 7.6)
All https:// referrers are working fine. The only one giving a problem is the https://www.hocom-advies.nl which produces an url like this:
https://www.hocom-advies.nl/hocom-advies.nl which results in a TYPO3 error: Page not found! ??
I have all rewriting in my Vhost. Only some basic TYPO3 rewrite stuff in the .htaccess file. And some basic TS lines in the config.
The same https request on an other TYPO3 8.7.2 system is working ok! Both settings in the VHost and TSconfig are equal.
So where to look for here? Any idea? Thanks.
your domain duplication can have multiple reasons:
have you configured config.absRefPrefix = / (or have you inserted your domain?)
don't use baseURL!
are your rewrites clean? (no missing protocols?)
do you generate links without protocol?
I have shifted from live site to local site, the product detail page is showing a 404 page. I tired re-index multiple time.clear cache. check database also but it still displays a 404 page.
There can be several things you can check:-
1. Check for url in core_config_data and also check cookie url.
2. Check on server for mod_rewrite module may be this is not enabled on local, this can also be the reason if you were using SEO friendly url.
Clear the cache once you are done with these. It will be great if you can tell how url for PDP page is been generated on local.
my url is like this
http://localhost/reyassoc/10x-a4-silver-diamond-brochure-island-stand.html
same it working on existing live site
Run below sql query
SELECT * FROM `core_config_data` WHERE path = "web/seo/use_rewrites";
See whether the value 1 or not, if the value is 1, try to change it to 0.
This value is for SEO friendly url, which removes index.php from your store url.
Also, you can replace your .htaccess file with default one in Magento root folder.
Your server may have problem with mod_rewrite module or its configuration, you may re-install it.
I developed a site in codeigniter with basic functionality now i want to update this site to my live server. But when i uploaded my site to live server it shows 404 - PAGE NOT FOUND.
http://www.nawtist.com/test/ams/
Please tell me what do i need to do. I searched a lot about this but i didn't found any helpful information. So is there any base_url or anything else that i need to change before upload this on live server really appreciate
And remember, many servers are case-sensitive and with CodeIgniter v3 you should change the controller's first letter file and model's first letter file to upper case. That worked for me too.
Best
You have problem with your htaccess file or mod_rewrite is disable on that server.
When you go to page with index.php it works (although css file doesn't work because of bad routing)
also check if $config['index_page']=''; if it should work without index.php
I had the same problem times ago and there are 4 points in codeigniter to care about as I remember:
Check base_url value in your "config.php"
Check database settings in "database.php"
Check .htaccess file contents if you have defined it once
Check routes.php if you have defined any custom routes
That's all!
If you are facing 404 page not found in Codeigniter after upload file local to live server then follow these steps
change your controller and file name first letter capital
same change as above in model class and file name i.e first letter capital
After following steps above your problem can be solve Thank you.
I am a magento newbie.
I've observed that when I make an installation of magento by copying all contents of the extraction directly to localhost.... i.e (when app, media, skin, index.php etc all pasted directly in localhost) I am unable to access the admin by simply typing in localhost/admin.
Whereas I have to type in localhost/index.php/admin to get into the admin panel.
Also when i click on any category i have the same problem.
I have to append index.php/ before the category name to get the category link working.
Can anyone please tell me how to get them working.
Check your Base URL in the Admin Panel, go to System | Configuration | Web and make sure the Secure and Unsecure Base URL does not include the 'index.php' part.
If you do not have index.php in my secure or unsecure web configuration and this happening on front end and back end, try to enable url rewrites and see if that solves it. You need mod_rewrite enabled on your localhost.
What is your local server?
I'm currently experiencing an issue whereby my MVC site is not responding correctly using IIS 6.
I've setup a url as http://mysite.co.uk which automatically redirects to the correct MVC home page. As the site contains sensitive information I have added the [RequireHttps] attribute to each controller class to automatically redirect the browser to an https url of https://mysite.co.uk which works correctly.
When I access the site as http://www.mysite.co.uk the site correctly redirects to https://www.mysite.co.uk/Default.aspx but it then responds with
Bad Request (Invalid Hostname)
It looks like any time I use www. as part of the url it fails to respond but I have a hostheader setup as www.mysite.co.uk under the IIS website. Is there anything in particular I need to do to make MVC understand the www. part of the url in terms of routing?
Thanks,
Brian.
IIS 6 doesn't add ssl host headers as you think it would. see my article at:
http://completedevelopment.blogspot.com/2009/06/multiple-host-headers-ssl-and-wcf.html