I am trying to configure my server to overwrite the c-ip value with the real user IP provided by the Load Balancer within the X-Forwarded-For header.
This was possible within IIS 7.0 and IIS 8.5 using the Advanced Logging module
(https://learn.microsoft.com/en-us/iis/extensions/advanced-logging-module/advanced-logging-for-iis-custom-logging)
but the module is not supported anymore in IIS 10.
Did anyone find an alternative of the Advanced Logging module for IIS 10? or at least to overwrite the c-ip values within the logs?
Thanks,
Cristian
it has been retired ...for older versions https://learn.microsoft.com/en-us/iis/extensions/advanced-logging-module/advanced-logging-for-iis-custom-logging
Related
I originally installed ColdFusion 11 in a local environment (windows 7) and selected "Use built in web server". Everything was working pretty good. Now months later, I realize I need to use a real web server for URL rewrites (Apache, IIS, etc) but there is no documentation I can find on how to do so.
I have attempted looking through the administrator's panel for any information, but couldn't even get a jumping off point. Any assistance would be greatly appreciated.
First, it sounds like you need to decide which web server you want/need to use and that could be determined by where you'll end up hosting your site. CF code is quite portable but if you're doing URL rewrites, file system access, etc... then you need to code those to match the production environment, otherwise you might find yourself having to rewrite and retest all that again.
As commented above, a lot of information about configuring CF for web servers is available by searching. You'll first need to install & configure your web server, so search around that first. Then you'll need to configure the web server to understand which requests to pass to ColdFusion's engine.
If it's IIS then you need to make sure IIS is installed and the following components are installed: ISAPI Extensions, ISAPI Filters, CGI, ASP .NET
Then configure an IIS site to point to your CF code and after that use the "Web Server Configuration Tool" application (installed with CF) that will associate the relevant file types with ColdFusion.
Most of the time it's as simple as that.
I have a web application that is running on WebSphere Liberty Profile 8.5.x, which is located in a private LAN. I have set up an IIS reverse proxy in a DMZ that points to the application server in the LAN and has a URL Rewrite outbound rule. URL Rewrite outbound rules will not work if the content is compressed.
I have zero experience with WebSphere, and the people who set up the application server are unavailable. I have searched and can't find any answers -- at least that I can understand with my lack of experience.
So, is there a way to disable compression in WebSphere Liberty Profile 8.5.x, and if so, how exactly do I go about doing it?
Instead of working with some reverse proxy config, I'd suggest you to install supported WebSphere Plugin for IIS.
You can download it from WebSphere for Developers downloads or if you have production license:
Web Server Plug-ins for IBM WebSphere Application Server Part 1 and Part 2
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swerpws-wasdevdl85
Then install plugin and configure for MS IIS
Then configure plugin to work with Liberty. Although this page is mentioning IBM Http Server, same configuration steps are for any web server supported by plugin.
It turns out I didn't need to change any WebSphere Liberty settings at all. Here's how I fixed it:
In the URL Rewrite module, I added the HTTP_ACCEPT_ENCODING server variable.
In the Server Variables section of the Inbound Rule, I added HTTP_ACCEPT_ENCODING with an arbitrary value (I used "asdf") and set Replace to true.
I edited the web.config, and changed the value of "HTTP_ACCEPT_ENCODING" serverVariables node to an empty string.
Now IIS only accepts non-compressed responses, and the Outbound Rule works as expected.
I have a problem with a web site running on an IIS 8.5 server that is not started automatically when the server reboots. The site is originally installed through ServerManager, where there is this line of code:
site.ServerAutoStart = false;
Now I would like to change this setting through the IIS Manager interface.
In IIS 7.5 i can set a web site to start automatically by setting the Start Automatically property under Advanced settings. But this setting is gone in IIS 8.5.
I found a solution to my problem inspired by this question:
How to config application pool in IIS 7.5 automatically re-start when it was stopped?
It is possible to access and edit all the detailed settings through the Configuration Editor, which can be accessed through the Features View in IIS Manager. I realize that in the link Mr Mo sent, the Configuration Editor was used, but it is not specified very clearly how to access it.
Check it out:
http://blogs.msdn.com/b/benjaminperkins/archive/2014/01/07/configure-the-iis-application-initialization-module.aspx
I think it will solve the issue.
When running our installer, we have it configured to setup 3 websites in IIS, before the upgrade this worked as expected, even if the default website (or any site listening on the same port) was still present.
If the website listening to Port 80 was already started, WiX would create the website from our installer, and just not start it (which is what I'd expect). Since upgrade to 3.7, however, what I've found is that the installer does not create the website if there is any other site configured in IIS that's listening to the same port.
Is there something missing in the WiX setup that I need to add to force WiX to add the website from our installer, or is this just a known issue with creating websites via WiX?
Edit:
Looking into this further, it appears that the website is checked by the port, rather than by name. If I have "Default Website" on port 80, any applications that are under the website I have in the installer are configured under the Default Website.
The IIS CustomActions in the WiX toolset use the "natural key" to find the web site which is the ip:port:header combination. Most websites, only the port is specified. In you scenario, I expect the WiX toolset found the existing website and "fixed it" based on the specifications in your installation package.
Thanks Rob, I managed to fix the issue by setting the ConfigureIfExists flag to true, which created the site as I'd expected it to originally.
I've been trying for days to get Tomcat up and running through IIS via the Jakarta Connector.
I've followed all of Microsoft's instructions -- put the connector .dll in %tomcatdir%\bin\win32\i386\, added the registry entry, added a filter (pointing to the .dll) to the default web site... and yet, any time I try to access a Tomcat web app, I get the "You are not authorized to view this page" error.
Has anyone experienced this? Help!
Thanks,
-Dan
http://archive.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win32/jk-1.2.14/isapi_redirect-1.2.14.exe
I use this redirect with Tomcat 5.5 and IIS 5 or 6. I haven't tried it with IIS 7.
You have to modify the uriworkermap.properties file to choose which paths to redirect, but besides that it works pretty much straight up. It adds all the registry garbage for you.
Ah, except on IIS 6 you have to add the isapi redirect.dll into its application whitelist.
Try this mate, it can help you.
http://itgration.blogspot.com/2016/04/configuring-tomcat-connector-for-iis-8.html
It tells you how to configure access to tomcat website via IIS and the necessary to set up tomcat server as a windows service and then forward the website to IIS via port 80. You will do this by installing a custom ISAPI filter in IIS that understands how to use the AJP protocol (Apache JServ Protocol) to communicate with tomcat. The main idea is to use Tomcat Connector ISAPI available to download from apache web site.
I used it with IIS 8 and 7