如何使用IRequiresRequestStream将xml文件发布到ServiceStack

在阅读了关于这个主题的几个不同的SO帖子和文档后,我仍然感到困惑,无法通过我的服务端点上的RequestBindingException.例如,我想使用POSTMAN将以下xml发布到服务.

  
    daffy.duck@example.com
    Joey
    Disney
    Duck
    1 Disneyland Street
    2 Disneyland Street
    PAUMA VALLEY
    CA   
    92503
  


[Restrict(RequestAttributes.Xml)]
public class LeadData : IRequiresRequestStream
{
    public Stream RequestStream { get; set; }
}

public object Post(ServiceModel.Types.DirectApi.Legacy.LeadData request)
{
    return null;
}

Routes.Add("/Leads/LeadData/", "POST", "LMS - DirectApi")

我希望这将是克服.NET反序列化属性排序问题的最佳方法.

原始请求/响应

POST http://localhost/LO.Leads.Receiver/api/Leads/LeadData/ HTTP/1.1
Host: localhost
Connection: keep-alive
Content-Length: 381
Origin: chrome-extension://aejoelaoggembcahagimdiliamlcdmfm
User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2289.0 Safari/537.36
Content-Type: application/xml
Accept: */*
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.8
COOKIE: ss-pid=fhjNz7BGBBqgps6zsnUo; ss-opt=perm; X-UAId=f94092eb-fae8-4b39-b5ff-ae3b404645d8; m=34e2:|41b8:f|4a01:t|ca3:t|b12:f|47ba:t|77cb:t


  
    daffy.duck@example.com
    Joey
    Disney
    Duck
    1 Disneyland Street
    2 Disneyland Street
    PAUMA VALLEY
    CA   
    92503
  


HTTP/1.1 400 Bad Request
Cache-Control: private
Content-Type: application/xml
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-MiniProfiler-Ids: ["6f4255ee84fa45d1a2e05de8a268fc37","a52523648aed4dfaae96e607d07b5163","f9cf295e8e7b4aa1b0579929e61d59a5","7b4daa97fc8d427cb952b17414c4da31","707e7624fa4546c3911a9cb3ce5e6a36"]
X-Powered-By: ASP.NET
Date: Wed, 28 Jan 2015 02:19:30 GMT
Content-Length: 538

RequestBindingExceptionUnable to bind request   at ServiceStack.Host.RestHandler.CreateRequest(IRequest httpReq, IRestPath restPath)
   at ServiceStack.Host.RestHandler.ProcessRequestAsync(IRequest httpReq, IResponse httpRes, String operationName)

谢谢你,斯蒂芬

由于Request Content-Type与现有的已注册的Serializer(即XML)匹配,因此它仍然会尝试使用该Serializer对正文进行反序列化.现在修复了忽略来自此提交的IRequiresRequestStream请求的所有序列化程序.

现在,您可以使用以下命令创建对流的访问并将其读取为普通XML:

[Restrict(RequestAttributes.Xml)]
[Route("/Leads/LeadData/", "POST", Notes = "LMS - DirectApi")]
public class CustomXml : IRequiresRequestStream
{
    public Stream RequestStream { get; set; }
}

public class RawRequestService : IService
{
    public object Any(CustomXml request)
    {
        var xml = request.RequestStream.ReadFully().FromUtf8Bytes();
        return xml;
    }
}

您可以使用HTTP Utils调用,例如:

var xml = @"
                
                daffy.duck@example.com
                Joey
                Disney
                Duck
                1 Disneyland Street
                2 Disneyland Street
                PAUMA VALLEY
                CA   
                92503
                
            ";

var requestUrl = Config.ServiceStackBaseUri + "/Leads/LeadData/";
var respOnseXml= requestUrl.PostXmlToUrl(xml);

Assert.That(responseXml, Is.EqualTo(xml));

此更改可从v4.0.37 +获得,现在可在MyGet上使用.如果您更改了使用不同Content-Type的请求(例如application/xml-lead,与任何现有Seri​​alizer不匹配),那么它之前也会有效,但是您需要删除[Restrict]仅允许XML请求的内容.