Extending the web application to support both HTTP and HTTPS ASP.NET C#

Question

0.00/5 (No votes)

See more:

Dear All,

I have created ASP.NET C# web application and "Extended the web application to support both HTTP and HTTPS".

Http Port# 80, Https Port# 443.

What I have tried:

Now, I have created another web application and when i'm extending this to support both HTTP AND HTTPS.

I'm getting alerts that, http Port# 80 already used, so, i changed to 8080 and now what port# should i give to Https, because, Port#443 is already used.

Actually i want to know, what are the ports# we can assign to HTTP & HTTPS.

Can any one please help me.

Thanks

Posted 6-Dec-17 20:00pm

abdul subhan mohammed

Updated 7-Dec-17 2:57am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nathan Minier · Answer 1 · 2017-12-07T02:57:00

As a developer, unless you're providing your own web server bundled with your application you generally want to let the System Admins handle the ports on the host machine.

As you're using ASP.NET, I'm assuming that IIS the web server. Don't put logic in place to manage ports in this instance, just logic that will refuse to send sensitive data if the port is not encrypted (!Request.IsSecureConnection).

If for some reason you've rolled your own web server, and are using 8080 for HTTP, it would logically follow to use 8443 for HTTPS. Again, though, I would suggest this only as a default and make this value configurable, since you do not know what environment your software might be operating on and local SAs might have different requirements.

The core point is that you should not be trying to manage the server. There's an SA that does this. In a perfect world, your application doesn't even understand that it's using HTTP(S), that's been abstracted away from it.