I tested the TYPO3 extension secure_downloads on development site, and it worked fine. When I installed it with identical settings on the production server, which uses HTTPS, it failed to generate the secure links.
This is under TYPO3 6.2 LTS, and version 2.0.3 of the extension.
I thought that the extension https_enforcer might be an issue, but the problem persists after removing that.
Thank you.
In the extension configuration, you can force the HTTPS by configuring
Parsing | Domain [basic.domain]
to the full https://example.com/
While that setting is supposedly "not needed for internal (relative) links," it is needed if you want to always use a secure connection.
Related
I provided incorrect subdomain name during Kabanero Foundation installation on OKD. Now my Application-->Routes are wrong. How to fix that?
For Kabanero Landing Page, my link is: https://kabanero-landing-kabanero./
I tried https://kabanero-landing-kabanero./ but I get
Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
Expected: Kabanero Landing Page
Actual: Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
There really is no good way to fix it. There is not a good manner to change the routes automatically. Assuming you are early in your install, you should be able to clone the 0.2.0 (if you installed 0.2.0) support scripts from https://github.com/kabanero-io/kabanero-foundation/tree/0.2.0/scripts and run the uninstall-kabanero-foundation.sh script to remove the foundation and reinstall. You should be able to keep the OKD install that you have done.
If there are enough people that hit this, I can put a requirement in place to provide an update script to change this value and restart.
Whenever I start it, it sends an HSTS header which means every request now redirects from http://localhost to https://localhost.
This is a PITA when developing locally with node.js.
Is there a way to stop it from doing that?
I believe this has been fixed in recent builds. Try re-installing the latest build?
I'm developing some HTML-files using a lot of different libraries, but everything is compiled and served using grunt ('grunt serve'), which fires up my default browser and connects on 127.0.0.1:9000. I can copy/paste that URL into other browsers on my OS (Mac OS X) with no issues.
However, I also need to test in IE, where I normally use VirtualBox with browsers from modern.ie, but the URL is not available on those images (which makes perfect sense as it's a local IP). How do I make those URL's available to my VirtualBox images?
If I use my MAMP setup, I can access the URL's I've configured in my hosts file, but as I'm not using MAMP for this, that won't be an option.
Thanx in advance for any help!
/kim
Managed to get it to work, and as hgoebl said, it was a purely networking issue. Basically, I just followed this: http://naxoc.net/2013/10/22/windows-in-virtualbox-on-the-mac/ and everything works now.
I've added the following XML to my SiteUrls.config file:
<RewriterRule>
<SendTo>/pod/</SendTo>
<LookFor>.*abcdefg</LookFor>
</RewriterRule>
When I go to http://localhost/abcdefg it successfully redirects me to http://localhost/pod. My localhost is an IIS 7 web server.
However, I am unable to get this same exact configuration to work on our production or staging machines. It stays on http://staging.x.com/abcdefg and gives a 404 error.
What exactly needs to be set up to allow this to work? I have not noticed much difference between the IIS modules I have locally and the IIS modules on the production/staging systems.
You may need to install a hotfix to support extensionless URLs on IIS 7.
From Hanselman:
Getting extensionless URLs working on IIS6 was tricky before and lots of been written on it. Early on in IIS6 and ASP.NET MVC you'd map everything . to managed code. ASP.NET Routing used to require RAMFARR set to true until the Extensionless URL feature was created.
Extentionless URLs support was added in this KB http://support.microsoft.com/kb/980368 and ships with ASP.NET MVC 4. If you have ASP.NET MVC 4, you have Extentionless URLs on your development machine. But your server may not. You may need to install this hotfix, or turn on RAMMFAR. I would rather you install the update than turn on RAMMFAR if you can avoid it. The Run All Modules options is really a wildcard mapping.
I'm working on (surprise) a web framework that entirely is dependent on mod_rewrite, however I'd like for it to be compatible with IIS ( if possible ). There's a slight slight chance one of the sites being built will have to be stored on an IIS box, I'm wondering if there's any rewrite module in the most popular versions of IIS I could rely on.
IIS7 is easy--use the URL rewrite module as Garethm points out.
IIS<7 is a bit trickier--no integrated pipeline to latch on to. Presuming you can require that persons hosting on IIS have dedicated hosting, or can at least get an ISAPI module installed, check out iconic's Isapi Rewrite Filter. It is free, open source and pretty much mimic's mod-rewrite.
For IIS7, there is the IIS URL Rewrite Module. If I remember correctly, you can install it with the Web Platform Installer.
There also appears to be a company that has rewritten a rewriting module for IIS that is compatible with Apache's mod_rewrite configuration format. You can find out about it on the Micronovea website. I have no experience with this one though.
I've used HeliconTech's ISAPI_Rewite with great success. It's not free or open source but it's reasonably cheap and well supported, also super-easy to install and get running.
Helicon also have a 'lite' version that is free.