-
Posted to
IIS7 - General
by
WenJun Zhang - MSFT
on
11-20-2009, 4:49 AM
Sure, the data will still be encrypted when using self-signed certificate. The risk Anil mentioned is about you can no longer *100%* ensure the web site you connect to is the site you want when using self-signed cert. Please refer to:
http://www.sslshopper.com/article-when-are-self-signed-certificates-acceptable.html
-
Posted to
IIS7 - Publishing
by
WenJun Zhang - MSFT
on
11-17-2009, 5:10 AM
Please try using IE File->Open->Open as web folder to open you webdav path and upload a file. See if this succeeds. If not, gather corresponding IIS logs and post them here for us to take a look.
-
Posted to
IIS7 - General
by
WenJun Zhang - MSFT
on
11-17-2009, 5:08 AM
If you can retrieve the corresponding FTP log entries, please post them here for us to take a look.
-
Posted to
Troubleshooting
by
WenJun Zhang - MSFT
on
11-17-2009, 5:02 AM
Please also try changing the web site's application pool's identity to the custom user account. Also make sure it's added to IIS_WPG group. Then please run the page again and check the results.
-
Posted to
Security
by
WenJun Zhang - MSFT
on
11-11-2009, 5:49 AM
Hi Patrick,
This is the correct solution for your problem. The priority of UrlScan should be lower than sspifilt.
-
Posted to
IIS7 - Publishing
by
WenJun Zhang - MSFT
on
11-11-2009, 5:47 AM
Do you have the Microsoft sharepoint administration site in IIS? If so, you can browse to this site to open FPSE admin. Please ensure it's running in a 32bit application pool.
-
Posted to
IIS in SySWoW Mode
by
WenJun Zhang - MSFT
on
11-10-2009, 4:56 AM
Make sure the authenticated identity has Read/Write NTFS permission on System temp directory. If anonymous access is allowed, the account should be IUSR_<machinename> .
If still no success, run tools like process monitor to track down the I/O of w3wp.exe process and repro the issue. It will show you where the denied access is.
-
Posted to
Configuration & Scripting
by
WenJun Zhang - MSFT
on
11-10-2009, 4:20 AM
Hi,
As I known, there is no group policy can control p3p headers on IIS. The built-in way to use p3p headers is documented in below article. Of course, we can also set the headers by code or custom ISAPI. I'd suggest you verify if there is any special ISAPI filter configured on your IIS server(or ISA?) which may be the root ...
-
Posted to
IIS7 - Security
by
WenJun Zhang - MSFT
on
11-09-2009, 5:40 AM
This is actually based on IE behavior. Please check out below article. It contains all info which explains your problem:
http://support.microsoft.com/Default.aspx?id=258063
-
Posted to
Web Deployment Tool (MS Deploy)
by
WenJun Zhang - MSFT
on
11-09-2009, 5:37 AM
Hi Mike,
On your IIS7 server, please check application pool used by your destination site and verify the .net framework version. By default, it's .net fx 2.0 on IIS7 Windows 2008.