Hot answers tagged isapi
I published an ISAPI filter to work with our BIG-IP's and have just updated it with full x86 and x64 support. Check out the blog post I wrote on it a while ago. Just copy the enclosed F5XForwardedFor.dll to your server and reference it in the ISAPI section of your virtual site. http://devcentral.f5.com/weblogs/joe/archive/2005/09/23/1492.aspx
This is discussed in this thread of the IIS Microsoft Community. It seems there is a helper to do that for IIS (Especifically stated to work with Microsoft ARR but it should work for any reverse proxy or load balancer).
If you are adding a filter at the site level, a restart is not required - but you do need to make at least 1 request to the website for the filter to "load". If you are adding a filter at the global level, a restart is required. http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/54c41c83-3723-4695-9bf1-9f7b1f674be0.mspx?mfr=true ...
The clue to solving this is in the error message (IIS is really good at explaining 500.19 errors which is nice): This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the ...
If you rewrite outside of the host, e.g. http://x/ -> http://x:999/, you are asking the client to redirect, which means it will show up on the client side. You need a proxy server to do this. Try Squid, Varnish, mod_proxy.
Check NTFS permissions on .htaccess files and make sure you are not using the Lite version of ISAPI_Rewrite. In the .htaccess files themselves make sure you have RewriteEngine on at the top of each file. Edit to add: Put these lines in your httpd.conf file and reload the service. They will create error and rewriter log files. Checking the event ...
It sounds like IIS 6 is caching your web pages (you didn't define if you were using Apache or not, so I assumed as it's a Windows server) Use this link from Microsoft and set the site to Expire Immediately.
If you're seeing a "Filter XYZ.DLL failed to load from (path that implies 32/64-bitness)", try toggling the App Pool's bitness first, in the "Enable 32 Bit App" property setting. There's File System and Registry redirection which makes life trickier for Sysadmins (though no trickier for app developers, so it's a mixed blessing) on 64-bit Windows platforms, ...
Couldn't think of a way of doing this through IIS as easily as editing the configuration for WebSphere. I don't use WebSphere, but the docs suggest it's possible to include or exclude UriGroups using Route rules: UriGroup A group of URIs that will be specified on the HTTP request line. The same application server must be able to handle the URIs. The route ...
What you could do is Prepare an unattended installation of IIS7.0 (only add the components you need) Use either appCmd or the IIS 7 powershell snap-in to create the vDirs and configure the handler mappings Execute from a vbscript or batch
Make sure the user that is failing trusts your ldap server's certificate authority. To do that, log in as the user that is failing (you might have to grant temporary privileges for that, maybe put it in the "Remote Desktop" group). Start certmgr.msc and look for the certificate authority you are using under "Trusted Root Certification Authorities". ...
Only top voted, non community-wiki answers of a minimum length are eligible