Secure Connection Failed

Question

0.00/5 (No votes)

See more:

I hosted my asp.net code in IIS7.0 as a website and for a single aspx page in "Features View" tab enabled the SSL Settings with client certificate required option.

I created a new "Self-signed certificate" in iis.

When i access that particular page without https it correctly shows "The page you are trying to access is secured with Secure Sockets Layer (SSL)." error. But the problem is when i acess the page with https it is showing me the error

Quote:
Secure Connection Failed
An error occurred during a connection to localhost:1141.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.

Pls help me with this error...

I NEED TO PROVIDE HTTPS address for only one page in my website.

Posted 26-Feb-13 22:38pm

Member 9845850

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)

Kevin Johnson SSL · Answer 1 · 2013-03-19T23:33:00

Solution 1

Have you set the SSL port directive in IIS to 443? Perhaps if you can show your IIS config?

Also this MS support article may help you: http://support.microsoft.com/kb/324069[^]

Posted 19-Mar-13 23:33pm

Kevin Johnson SSL