SSL Certificates and Azure Web Apps

Use it or lose it. The good thing about getting a cert with a 3-year expiration period is that I don't have to worry about it for 3 years. The bad thing is that I forget how in the world I did it last time. I waited until the last minute (or last three hours) to renew a cert today for an Azure web app.

A call to GoDaddy support led to a statement saying that because Microsoft hasn't provided them with documentation, they can't provide their customers with assistance due to potential liability issues.

Of course, there are plenty of blog posts written about this in various forms, but even an Azure post wasn't quite helpful for my lack of knowledge in this area. But this one was. So glad people document things like this.

Tested with IE, Chrome, Safari...oh wait

When I start a new project, particularly when doing a POC, I'll often grab something I've done in the past that is similar and begin to tweak from there. But as POCs tend to evolve, problems occur when my assumptions remain the same. That "tested with..." disclaimer tag that came across from the borrowed project just won't cut it as is.

Case in point: a pretty important line of code that can help generate revenue. Turns out this didn't work with Safari / Chrome:

$('#btnSubmit').trigger('submit');

But this does:

$('form#ajaxForm').trigger('submit');

A good reminder to actually test and not assume. I'm glad I have a co-worker who has a knack for breaking things before customers do.