So I encountered this scenario where the SSL was replaced but the site is still serving the old SSL on a site hosted on IIS 8. You keep checking it on the IIS manager but its already set to the correct SSL Certificate but still you are being presented when browsing the site with an old SSL. How do you solve it ?
It turns out the IIS 8 may have keep another SSL record on its own metabase. You need to reset this in order for the SSL Cert that you've added to take over.
First things first, get the thumprint of your SSL. This is gathered by doubleclicking the Certificate from the MMC (certificate snap-in) and then browsing the properties and looking up the Thumbprint similar to the one shown below :
Then run this command on your server :
Now look at the list of SSL Certs if IP and Port Number in the list has a different thumbprint with the correct SSL. If it is, then most likely the IIS is serving the incorrect SSL.
You can delete this on your server by using the command :
Make sure to specify the correct ipport values, which is similar to the IPPort values on the list earlier.
When done, restart your IIS and then re-assign the SSL Certificate to your site.
Afterwards browse and you will see that your site is serving the correct SSL Certificate.
Please leave comments if this helped you.
Friday, May 16, 2014
Tuesday, May 13, 2014
Using NServiceBus Serialization
While working on a project, we had a requirement to send a message to a NServiceBus hosted queue. We realized that normal sending of message to that queue does not work as NServiceBus wraps some header on the message. This either mean we need to send a message using NServiceBus or create an application that uses Bus.Send. Unfortunately we don't want to use Bus.Send so we just re-used the XMLSerialization of NServiceBus.
Here's the code :
MyMessage walletMessage = new MyMessage ();
IMessageMapper messageMapper = new MessageMapper ();
Type type = messageMapper.GetMappedTypeFor( typeof( MyMessage ));
messageMapper.Initialize( new[] { type });
NServiceBus.Serialization.IMessageSerializer messageSerializer
= new XmlMessageSerializer (messageMapper);
using ( Stream stream = new MemoryStream ()){
messageSerializer.Serialize( new object[] {
walletMessage }, stream);
stream.Position = 0;
var sr = new StreamReader (stream);
var variableToSendToQueue = sr.ReadToEnd();
}
Here's the code :
MyMessage walletMessage = new MyMessage ();
IMessageMapper messageMapper = new MessageMapper ();
Type type = messageMapper.GetMappedTypeFor( typeof( MyMessage ));
messageMapper.Initialize( new[] { type });
NServiceBus.Serialization.IMessageSerializer messageSerializer
= new XmlMessageSerializer (messageMapper);
using ( Stream stream = new MemoryStream ()){
messageSerializer.Serialize( new object[] {
walletMessage }, stream);
stream.Position = 0;
var sr = new StreamReader (stream);
var variableToSendToQueue = sr.ReadToEnd();
}
Subscribe to:
Posts (Atom)
-
So we have an EC2 instance on AWS. But we need to terminate it as the project has to give way to something urgent and therefore not on for...
-
When updating MacOS High Sierra, you may experience this issue, where a couple of hours, you will be presented with an error Disk Management...