I have an asp.net VB site I am hosting at home. I have a domain with godaddy (for example lets call it www.mywebsite.com). This is web forwarded with masking to a freeDNS name called mywebsiteMoo:1111 which is in turn forwarded to my IP. As I have web forwarding with masking turned on the user only sees www.mywebsite.com but I am having trouble and I am sure its something daft.
From the first page of my website there are some links to other pages so for example page2.aspx. If I use page2Link.NavigateURL="page2.aspx"I get a 404 error when it tries to navigate there.
Is there something fundamental I am doing wrong?
Related
we have multiple local IIS (asp.net) websites in our local server that can access via static IP from Internet. Each website has own authentication for itself(forms authentication).
We need a master website that our static IP redirect to it, and after authentication(forms) can access to another sites by link(after second authentication for each site that opened).
I tried virtual directory and got error for WEBCONFIG, after that use applications under master website, also got error because of multiple authentication(without master authentication works perfectly).
Is there a way to have multi form authentication for that?
Thank a lot.
We use firewall accounting for it. When an IP receive by firewall, redirect to a login page that use AD for authenticating.
I have a website hosted on Azure and SSL-enabled. I have a silly question:
Everything can still be accessed without https (e.g. "http://www.teacherspet.net.au"). How do I force everything except for the home page (which doesn't need login) to go https?
In other words, when people type in "http://www.teacherspet.net.au", it is redirected to "https://www.teacherspet.net.au".
I have an ASP.NET web forms application that requires that requires that a user log in.
I have had the application running on a live server with an IP address pointing at it, to allow external customers to test it. e.g. http://1.2.3.4/application
Last week the customers decided that they were happy to switch their users to my application, and asked us to switch the existing URL across to it e.g. http://www.applicationurl.com
As soon as we did this, the login page stopped working:
- if you log in with an incorrect username or password, it correctly tells you that you have made a mistake
- if you log in with a correct username and password, no error message displays, but instead of redirecting to the next page, the user is redirected back to the login page
Just to be clear, no changes were made to the application - it is still running on the same server with the same config settings. If I log on using either the internal or external IP address then the application works fine - once logged on I am redirected to the default page; it is only when using the external URL that I keep getting redirected back to the login page. The .css and images all load correctly for the login page.
This is .NET 3.5 running on IIS7 on Windows Server 2003.
Could you check web.config file's forms Element for authentication:
Check the path attiribute. is it "/".
Check the domain (if set).
On consultation with our IT team, I learned that the company that supplies us with DNS names was proxying the calls to our web server. When we switched the domain name to directly calling our IP address, the issue was resolved. I guess the proxy must have been modifying the HTTP calls or blocking cookies or something.
The way to check whether this is happening is to ping your domain - in our case, it was returning the IP address and domain name of our DNS supplier rather than the IP address of our web server.
More specifically, I am writing a web request handler that forks requests to different processing pages for separate, distinct ASP.NET web applications. Specifically, this handler's purpose is for handling Paypal's Instant Payment Notifications.
I'd like to know how I can expose those custom processing pages to localhost only, so that my forking handler's POSTS will go through, but remote machines cannot post to those pages directly.
IIS can be configured to only allow certain IP addresses to access a site. These settings can be found on the directory security tab for the site (IIS6) or in the IP address and domain restrictions option (IIS7). You can restrict this to local requests only be specifying the only allowed address to be 127.0.0.1
In IIS Manager, in the Bindings action panel for the site you only want to allow local access to, change the IP address to be 127.0.0.1.
For more than one application, set up several aliases in your Windows hosts file (system32\drivers\etc\hosts) for 127.0.0.1. Back on the Bindings action panel, set the hostname for each site to be one of those aliases, and use that alias in your GETs or POSTs from the other sites, such as httpx://mylocalsite/default.aspx.
If you can't isolate an entire site, then you can write an HttpModule, and in the BeginRequest event, throw an error if Request.IsLocal isn't true for the pages you're concerned about.
Well, i do not know how to do it in IIS, but your pages can check
Request.IsLocal
Hi I am hoping for some advice.
I have just managed to get a .co domain so I wish to point all requests from my .co.nz domain to the .co
I am running IIS7.5
I have created a services site e.g. services.mydomain.co.nz and the website mydomain.co.nz both are running on their own website and app pool.
At the moment I don't want to break any of the web services so I want to keep the services site as services.mydomain.co.nz but I want to automatically redirect website users to the .co domain instead of .co.nz
So far I have added a new host header in IIS and this allows me to hit the website using the .co domain but I can still hit the site using .co.nz
Do I need to create a url rewrite function to help with this?
You can use http redirection in IIS to direct all requests at the old domain to exactly the same path at the new domain.
You want to choose options as I have in this photo:
Include the full base url to the new site, ending at the slash after the domain name. then leave the other options as I have them; this way, any request at the old domain will be sent a 301 "permanent" code to redirect to the new, equivalent page on the new site.
Note that it's important that you do not check the first of those checkboxes under 'Redirect Behavior'; that will make it send all requests to the home page of your site, rather than to the same path url.
This should be on a separate IIS site, by the way.