Testing posting by email with a picture of the moon from last night...

I've extended BlogEngine.NET to post by email. Not horrible for the very specific case of this blog and a short list of email clients. I shudder to think of extending it to the general emails and different templates.

Add your comment...

Related Posts

• Migrating from Blogger to BlogEngine.NET
• Geotagging posts in BlogEngine.NET
• The curious case of the missing slugs (in BlogEngine.net 2.8)
• Fight Facebook with Email
• Converting Blogger ATOM export to BlogML

(All Code Posts)

(Published to the Fediverse as: Moon on a Wire #code #blogengine.net Picture of the Moon close to a wire. This is actually a test of posting by email from blogengine.net. )

Wasted far too long on trying to get WCF to work with custom basic authentication this week. Custom in the sense that I need to look up the username and password in a database and not have IIS attempt to match the credentials to a Windows account. Given how well WCF 4.0 supports RESTful services in general it’s a bit shocking that basic auth over SSL isn’t supported out of the box. It seems like you should be able to derive and hook up a class from UserNamePasswordValidator, set the transport clientCredentialType to Basic and be ready to go. I’ve heard that this works for self-hosted services, but no dice in IIS.

Basic access authentication is a simple protocol and so in the end I added a helper method that checks for access (and in my case returns the user information for later use) at the start of each call into the service. It’s very simple:

1. Check WebOperationContext.Current.IncomingRequest.Headers for an ‘Authorization’ header. If it’s there decode and validate the credentials.
2. If the header is missing or the credentials are incorrect add the WWW-Authenticate header to the response - WebOperationContext.Current.OutgoingResponse.Headers.Add("WWW-Authenticate: Basic realm=\"myrealm\""); – and then throw a WebFaultException with a 401 Unauthorized status code.

This triggers a browser to prompt for your username and password and then try the request again. When calling the service in code you can add the ‘Authorization’ header preemptively and skip the 401 response entirely.

Add your comment...

Related Posts

• Outlook/Office iCal feed 400 bad request error with C# WebClient
• BadImageFormatException for a 64-bit ASP MVC web application
• Space and multibyte character encoding for posting to Twitter using OAuth
• Reboot computer in C# / .NET
• Reading and Writing Office 365 Excel from a Console app using the Microsoft.Graph C# Client API

(All Code Posts)

(Published to the Fediverse as: Basic HTTP auth for an IIS hosted WCF 4 RESTful service #code #wcf #iis #rest How to implement .NET Basic HTTP auth for an IIS hosted WCF 4 REST API. )

Two new Catfood releases.

Catfood WebCamSaver 3.10 adds support for simultaneous updates in 4 and 16-cam modes. The WebCam Directory has also been completely overhauled. WebCamSaver is a rather voyeuristic screensaver that lets you watch live feeds from around the world. As well as a screensaver the feed is available in my World Webcams Google Gadget.

Catfood PdfScan 1.20 follows hot on the heels of 1.10. The main update is showing a preview of each scanned page which is super handy if you always forget which way pages are supposed to go in your document feeder. Mentioning no names…

Add your comment...

Related Posts

• Catfood WebCamSaver
• World Webcams 2
• World Time Lapse
• Catfood Weather 2.20
• Catfood Earth

(All Code Posts)

(Published to the Fediverse as: Catfood: WebCamSaver and PdfScan #code #webcamsaver #pdf #pdfscan Latest updates to Catfood WebCamSaver and Catfood PdfScan )

I’ve just moved ITHCWY comments over to Disqus. BlogEngine.NET now supports Disqus out of the box, but doesn’t export comments to anything that Disqus is willing to eat. I’ve knocked up a quick converter that takes a full BlogML export from BlogEngine.NET (and at least in theory any other source of BlogML) and converts the comments to WXR. You can import the WXR file under the Generic option in Disqus.

The tool is a Windows console application that takes two parameters, the BlogML import file and the WXR output, i.e.:

BlogMLtoDisqus.exe C:\BlogML.xml C:\ForDisqus.wxr

It isn’t fancy and there is no error checking so it will either work or die horribly. If the latter, leave a comment and I’ll try to fix it for you.

Download BlogMLtoDisqus.exe. You’ll need to install .NET 4.0 as well if you don’t already have it.

Updated 2011-04-22: Added an optional third parameter that specifies the XML namespace for BlogML in case you need to override the default.

Add your comment...

Related Posts

• Converting Blogger ATOM export to BlogML
• Migrating from Blogger to BlogEngine.NET
• Commentary
• How to get SEO credit for Facebook Comments (the missing manual)
• The curious case of the missing slugs (in BlogEngine.net 2.8)

(All Code Posts)

(Published to the Fediverse as: Convert BlogML comments to WXR for Disqus #code #blogengine.net #c# #.net #blogml #wxr #disqus A command line tool to convert BlogML comments to WXR (i.e. for Disqus). )