ServiceStack cross-origin request/ response headers

gistfile1.txt

Request URL:http://localhost:63005/utils/md5/test
Request Method:OPTIONS
Status Code:200 OK

Request Headers

Accept:*/*
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Access-Control-Request-Headers:origin, content-type, accept
Access-Control-Request-Method:GET
Connection:keep-alive
Host:localhost:63005
Origin:http://localhost:49391
Referer:http://localhost:49391/md5
User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.17 Safari/537.11

Response Headers

Cache-Control:private
Content-Length:0
Date:Mon, 08 Oct 2012 19:10:07 GMT
Server:Microsoft-IIS/8.0
X-AspNet-Version:4.0.30319
X-Powered-By:ASP.NET
X-SourceFiles:=?UTF-8?B?QzpcVXNlcnNcY2RlcHBlblxDb2RlXFV0aWxzXHNyY1xBcGlcdXRpbHNcbWQ1XHRlc3Q=?=

I upgraded SS and implemented the new API to include the following. Works like a charm. Thanks.

[Route("/utils/md5/{value*}")]
public class MD5Hash
{
    public string Value { get; set; }
}

[EnableCors(allowedHeaders: "Content-Type, X-Requested-With")]
public void Options(MD5Hash request)
{
}

public object Get(MD5Hash request)
{
    return new MD5HashResponse { Result = request.Value.ToMD5() };
}

Then just had to include this in AppHost:

SetConfig(new EndpointHostConfig
    {
        GlobalResponseHeaders =
            {
                {"Access-Control-Allow-Origin", "*"}
            }
    });

Sweet! glad to here it :)
Yeah it's probably a good idea to move to the new API, imo it's simpler more intuitive + requires less effort. We're slowly replacing all demos/examples to move to the new API on our side as well.