Just can't seem to get this one ...
I have an AWS Beanstalk app running on IIS. The load balancer is configured for SSL and so is the security group.
So, I enter http://www.example.org and it works.
I enter https://www.example.org and it works too. Running SSL, great!
Now, I want to force SSL, so my understanding from this thread (Redirect to https through url rewrite in IIS within elastic beanstalk's load balancer) is that I configure the health check and add the described rule in the web.config file.
When I enter http://www.example.org I should redirect to HTTPS, but it doesn't work for me?
I seem to have two web.config files, one under the Default IIS site and one under my own site (beneath the Default). This entry doesn't seem to work in either place, but bonks completely under the default site.
Any ideas about what I am doing wrong?
Okay, my last paragraph tipped me off.
I was exporting my application (locally) as a sub application of the IIS Default app. This same configuration translates to AWS - so AWS adds a rewrite rule in the Default app to point to the sub application you deployed.
I had two web.config files. One in the Default IIS app and the other in my application.
So, I changed my local config so my app WAS the Default and then exported and deployed the same configuration to AWS.
As the Default app in IIS the redirect works!
Related
I have deployed my meteor app to some random name/url. I own the actual URL I want , myapp.com, at Godaddy. I did not deploy to that URL literally because I did not understand how the URL at Godaddy was going to be used at meteor. I believed I would have to do something over at Godaddy after I deployed. Now, I am ready to deploy with myapp.com on the meteor command line. What is going to happen? What steps will I have to take to make sure the url is properly directed over to the galaxy servers? I have read this article and the CNAME for my URL at Godaddy is already set to Eastern Us galaxy server. How does all this work?
Edit:
So, I was able to deploy to www.myapp.com and this all worked. But then, when I wanted to type maypp.com into the browser, it failed. I was able to get to my site by typing www.myapp.com into the browser, but this is not what I want. When I deleted this app and redeployed to myapp.com, I could not connect no matter what and I was refused when generating the SSL certificate.
If your CNAME DNS record for myapp.com is set to point at the galaxy servers, then it should work once you run meteor deploy myapp.com. The mechanism behind this is a type of reverse proxy: The server that responds to the incoming HTTP(s) request will inspect the request and see under what name it was reached, in your case myapp.com. Based on that information, the reverse proxy redirects the request to the internal resource that runs your app.
I need path based routing in iis arr where i can create target group to assign different iis servers for web farm architecture. Which is provided by AWS Application Load Balancer.
For Example:
https://aws.amazon.com/blogs/aws/new-advanced-request-routing-for-aws-application-load-balancers/
I have to provide this kind of routing on my local machine using windows server IIS ARR(Application Request Routing)
Hey I need to configure this using target group which is provided by AWS ALB there is an option to set an instance in the target group for example:
I need this to be done on my local IIS machine using some third-party software.
I need something like this for my local IIS server.
As far as I know, if you want your ARR to achieve redirecting the request to the web farm according to special rule condition like http_cookie, http_host.
You could open the url rewrite rule in the IIS manamgent console and add some condition lik below image shows:
With lots of R&D, I found the answer that while crating multiple farms we can archive this
in my scenario I want to redirect my call to a specific IP but when I am using IP address the issue is due to IP so I create Farm for each IP and redirect my call to those farm due to that my issue of IP get solved so now I don't need to configure IP address to my web config file in my project.
I have two web apps setup in Azure, and for simplicity let's call them webapp1 and webapp2. They sit behind an application gateway, which is selecting the correct web app based on the subdirectory in the URL.
Here's a basic example of how I've set it up:
www.mydomain.com -> webapp1 (the default route)
www.mydomain.com/app -> webapp2
This is working fine, except for one problem: if webapp2 redirects to the login page, for example, the domain in the URL changes to the azurewebsites.net domain. Instead of redirecting to www.mydomain.com/login, it's going to webapp2.azurewebsites.net/login.
I'm fairly new to Azure application gateway, but I know it injects the x-forwarded-* and x-original-host headers. I assumed the gateway would either alter the redirected url request to correct the domain or the config on the web app would use the x-original-host instead. Neither of these things are happening.
Is there a way to configure either the web app or the gateway to make sure the host name doesn't change on redirects? Would this scenario work better with a separate web app/VM with a classic IIS reverse proxy setup instead of the application gateway?
Currently Application Gateway would not overwrite the response from the backend. We do inject X-Original-Host and your application should use that to write the redirect URL correctly back to mydomain.
Example to configure URL rewrite on web app can be found here. An example of rewriting default *.azurewebsites.net domain to a custom domain can be found here
I setup a Heroku app with vhost for subdomain handling. The app stopped responding to the custom domain originally assigned to it but the main Heroku app is live and working however, the subdomain link does not work for heroku. Please how can I fix this issue. app-name.herokuapp.com works. subdomain.app-name.herokuapp.com does not work. Also, customdomain.xyz does not work too.
All apps deployed on heroku actually are on subdomain of herokuapp.com so you can't create a subdomain for your app while using herokuapp.com for this you have to set custom domain, please follow the link to check how to set up custom domain.
I'm having a bit of an issue with an IIS web application. I copied all the application files from the server, registered the DLL files, set up my DB server locally and now I'm trying to run the application locally, on my machine. The thing is that the app checks the server domain name when you log in and my corporate domain name is not in the list of "allowed" domains so the logging in fails.
Could I edit some IIS application config file(s) to make it look like the web server is actually under a different domain name? I want to keep my machine, overall, in the current domain.
I don't think that you can change the config files in the IIS.