You searched for the word(s): userid:58807

More Search Options

RSS Available

• Re: HTTP Error 500.21 - Internal Server Error

  I ran into the same issue which turned out to be from a failed install of the framework. The framework folder was missing a number of files, including all of the aspnet* files. To get it working I ran the installer from this link: http://www.microsoft.com/downloads/details.aspx?FamilyID=ded875c8-fe5e-4cc9-b973-2171b61fe982&displaylang=en This is likely an issue with 1 of the installers for ASP.NET 4.0 Beta (1 or 2).

  Posted to Free For All (Forum) by OWScott on 10/23/2009

• Re: https page iframed inside a http page

  To have the iframes use https, just reference them with a fully qualified domain name (https://...). If it works by entering the URL directly into a browser, then it can be an iframe target too. However, keep in mind that if anyone is POSTing data back to the server, then your <form action > path should point to a secure page. Otherwise whatever they fill in and submit will be sent in plain text. To check if it's secure, most browsers will show you the properties of the iframe if you right

  Posted to Getting Started (Forum) by OWScott on 6/30/2009

• Re: "Cannot use a leading .. to exit above the top directory."

  To find out what is causing it, create a simple page that just says 'hello world' and see if it occurs for that. If it doesn't (and I assume it won't) then start adding parts of your site into the simple page until it breaks. Then you'll know what is causing it. The trick here is to narrow down to the actual piece that is causing it issue, then I suspect that the solution will become obvious.

  Posted to Free For All (Forum) by OWScott on 6/12/2009

• Re: IIS Website Host Header Name

  Let me see if I understand what is happening. From your first email, I got the impression that: - if you enter this in your browser: www.something.com/application-name/index.aspx it's redirected to http://localhost:portname/application-name/index.aspx or http://www.something.com:portnumber/application-name/index.aspx . If that occurs, then IIS is setup correctly and it's something with the website (the code . . . ie. aspx pages or global.asax, etc) that is causing that. The host header information

  Posted to Configuration and Deployment (Forum) by OWScott on 6/10/2009

• Re: IIS Website Host Header Name

  For the 2nd option, don't just ping the application. Instead, actually view it in the browser. The ping only tests the hosts entry level, but the web browser will test the site and provide more info.

  Posted to Configuration and Deployment (Forum) by OWScott on 6/10/2009

• Re: IIS Website Host Header Name

  There are 3 steps then: host entry -> confirmed good IIS binding -> likely good. You can confirm it by temporarily stopping the site and seeing if responds differently website itself -> my guess is that this is where the issue is. If it's redirecting from what you type in, to something else, that it's something in your website that is causing the redirect.

  Posted to Configuration and Deployment (Forum) by OWScott on 6/10/2009

• Re: "Cannot use a leading .. to exit above the top directory."

  This occurs when you reference something above the top directly. For example a page in the root folder that is using any type of path that has ../ in it will fail. IIS6 and later don't allow that by default. You can turn off that check in IIS if you have access to the server. It's just an IIS setting in IIS Manager. The alternative is to make sure that everything for your site lives under the path structure of the site so that you don't need to go up a level. The page is error isn't

  Posted to Free For All (Forum) by OWScott on 6/10/2009

• Re: IIS Website Host Header Name

  In that case, it does sound like it's possibly IIS related. nslookup won't work for this since it's hosts driven and not DNS driven. Since your ping test worked, you can assume that it's setup correctly. If you just have 1 site in IIS, I would suggest leaving the host header blank, setting the IP to All Unassigned and setting the port to 80. Then give it a test. If you can't use those generic settings, then make sure that you enter the IP address that you entered in the hosts

  Posted to Configuration and Deployment (Forum) by OWScott on 6/10/2009

• Re: IIS Website Host Header Name

  If I understand you correctly, you are entering a friendly domain name in the address bar but your site is redirecting to http://localhost:portnumber/ .... If it's doing a redirect, that sounds like something to do with the code or a redirect set somewhere. IIS is likely not the cause for that. In other words, your site is probably handling it just fine using www.something.com , but then something else on the site is causing the redirect. Try pointing IIS to a really simple page/site (i.e. simply

  Posted to Configuration and Deployment (Forum) by OWScott on 6/9/2009

• Re: IIS 6 redirect http to https impossible

  For the cert part, if you don't get a warning for sites that aren't using www, it's likely for one of the following reasons: they bought a cert that is for the root domain (without the www) they got a wildcard cert that supports the root domain the page isn't SSL, and when they go to SSL parts of the site, they redirect back to www For your redirect question, there are many ways to do that, as you've already found out. Another good option is ISAPI Rewrite ( www.isapirewrite.com

  Posted to Free For All (Forum) by OWScott on 6/6/2009