Databases
StackOverflow2013
Postsdbo
POSelf-hosted WCF Service with SSL on XP SP3
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSelf-hosted WCF Service with SSL on XP SP3
    primarykey
    data
    text
    <p>I've seen about 1000 posts on StackOverflow, blogs, and other sites, but none have been able to shed light on the problem I'm having. </p> <p>Setup:</p> <ul> <li>WCF self-hosted service (NOT IIS) using .NET Framework 3.5 (sorry, can't upgrade), WebHttpBinding</li> <li>A single endpoint using WebGet in the interface</li> <li>NO .config files -- everything is being created programmatically</li> <li>The service is bound to a custom port and NOT sharing a port with any other service or website</li> </ul> <p>Deployment targets:</p> <ul> <li>XP SP3, 2003, Vista, 7, 8, 2008</li> </ul> <p>Problem: On Vista, 7, 8, 2008 I have no problems. I'm getting the service up and running on HTTP as well as HTTPS with a self-signed certificate bound to localhost as well as the machine name on a custom port.</p> <ul> <li>BUT on XP, I can only get things working on HTTP, so I know the service itself is working properly. On HTTPS, I'm not able to make a connection because of an SSL failure. </li> <li>If I hit the URL directly in a browser, I see an SSL exception. </li> <li>In IE, it gives a warning that the certificate is not trusted. When I allow the exception, it gets to the service and executes. If I add <code>https://localhost</code> to trusted sites, I no longer see the warning and can hit the URL without issue.</li> <li>When I hit the same URL in Chrome, I get an Error 107 ERR_SSL_PROTOCOL_ERROR and I cannot bypass it.</li> <li>In Firefox, I get a ssl_error_rx_record_too_long error and it also cannot be bypassed. </li> </ul> <p>I've gone through several permutations of certificates and methods of assigning them to the service (httpcfg, etc.), all with the same results (or worse). So, instead of going back and forth trying to figure out what I've done and picking apart my existing settings, I have 2 questions:</p> <ol> <li>Is it even possible to create a trusted certificate on XP for localhost WITHOUT IIS and...</li> <li>What's the best way to bind it to a self-hosted WCF service with everything being done programmatically? I repeat this because other attempts to get assistance on these issues invariably leads to folks telling me what to put in a config file.</li> </ol> <p>Things to keep in mind: I already have this all working fine on Windows versions > XP/2003 under SSL with self-signed certificates, so I know the fundamentals are somewhat sound. I just can't seem to get the certificate set up under XP for localhost.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTshepang
    1. USjtalarico
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSelf-hosted WCF Service with SSL on XP SP3
      1. USjtalarico
      1. VTBountyStart
    2. VO
      singulars
      1. POSelf-hosted WCF Service with SSL on XP SP3
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSelf-hosted WCF Service with SSL on XP SP3
      1. This table or related slice is empty.
      1. VTBountyClose
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload