本文的目的是介绍asp.net–MVC4WebAPIAction返回：类型vsHttpResponseMessage的详细情况，特别关注mvcactionresult返回值类型的相关信息。我们将通过专
本文的目的是介绍asp.net – MVC 4 Web API Action返回：类型vs HttpResponseMessage的详细情况，特别关注mvc actionresult返回值类型的相关信息。我们将通过专业的研究、有关数据的分析等多种方式，为您呈现一个全面的了解asp.net – MVC 4 Web API Action返回：类型vs HttpResponseMessage的机会，同时也不会遗漏关于.net Web API 2,return HttpResponseMessage with ObjectContent、asp.net core WebApi 返回 HttpResponseMessage、ASP.NET Web Api HttpResponseException 400(错误请求)被IIS劫持、asp.net – .NET Web API HttpResponseMessage模式？的知识。
本文目录一览：- asp.net – MVC 4 Web API Action返回：类型vs HttpResponseMessage（mvc actionresult返回值类型）
- .net Web API 2,return HttpResponseMessage with ObjectContent
- asp.net core WebApi 返回 HttpResponseMessage
- ASP.NET Web Api HttpResponseException 400(错误请求)被IIS劫持
- asp.net – .NET Web API HttpResponseMessage模式？
asp.net – MVC 4 Web API Action返回：类型vs HttpResponseMessage（mvc actionresult返回值类型）
public class MyController : ApiController
{
public IEnumerable<MyType> Get()...
VS
返回HttpResponseMessage：
public class MyController : ApiController
{
public HttpResponseMessage Get()...
??
MVC是否将类型转换成HttpResponseMessage内容对象？除了显式添加格式化程序之外,页面上的结果看起来是一样的.
与客户有什么区别？
解决方法
如果你返回CLR类型,它将被HttpResponseMessage包装.
唯一的区别是,如果你返回HttpResponseMessage,你有机会直接使用HTTP工作 – 所以你可以设置头文件,绕过MediaTypeFormatter等等.
这一切都是个人偏好和/或在您的行动中执行的活动的问题.
.net Web API 2,return HttpResponseMessage with ObjectContent
public async TaskHttpResponseMessage Register(AllenRegistration model) { 1. Will return 400 Error return Request.CreateResponse( HttpStatusCode.BadReques t); 2. Will return Json Type like {return1:A,returnBL:B} return new HttpResponseMessa
public async Task
{
1.
Will return 400 Error
return Request.CreateResponse(HttpStatusCode.BadRequest);
2.
Will return Json Type like {"return1":"A","returnB"L:"B"}
return new HttpResponseMessage(HttpStatusCode.OK)
{Content = new ObjectContent
asp.net core WebApi 返回 HttpResponseMessage
ASP.NET WebApi 2 中的示例代码：
[Route("values/{id}")]
public async Task<HttpResponseMessage> Get(string id)
{
var response = Request.CreateResponse(HttpStatusCode.OK);
var accept = Request.Headers.Accept;
var result = await _valuesService.Get(id);
if (accept.Any(x => x.MediaType == "text/html"))
{
response.Content = new StringContent(result, Encoding.UTF8, "text/html");
}
else
{
response.Content = new StringContent(result, Encoding.UTF8, "text/plain");
}
return response;
}
ASP.NET Core WebApi 中的示例代码：
[Route("values/{id}")]
public async Task Get(string id)
{
var accept = Request.GetTypedHeaders().Accept;
var result = await _valuesService.Get(id);
var data = Encoding.UTF8.GetBytes(result);
if (accept.Any(x => x.MediaType == "text/html"))
{
Response.ContentType = "text/html";
}
else
{
Response.ContentType = "text/plain";
}
await Response.Body.WriteAsync(data, 0, data.Length);
}
可以看到，改变还是很大的，主要是两方面：
没有了 Request.CreateResponse，获取 Accept 需要通过 Request.GetTypedHeaders()。 没有返回值，而是直接通过数据流的方式写入到 Response.Body 中。
ASP.NET Web Api HttpResponseException 400(错误请求)被IIS劫持
[HttpPost]
public void Link(LinkDeviceModel model)
{
if (ModelState.IsValid)
{
try
{
model.Save();
}
catch (Exception ex)
{
ErrorSignal.FromCurrentContext().Raise(ex);
throw new HttpResponseException(ex.Message,HttpStatusCode.InternalServerError);
}
}
else
{
throw new HttpResponseException(HttpStatusCode.BadRequest);
}
}
这是我的提示请求：
POST http://localhost/myapp/service/link HTTP/1.1
Host: localhost
Content-Length: 112
Content-Type: application/json
Accept: application/json
{"DeviceUniqueId":"CC9C6FC0-7D06-11E1-8B0E-31564824019B","UserName": "me@mycompany.com"," Pin": "111111"}
而我的回答错误,充满了身体,回应：
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>IIS 7.5 Detailed Error - 400.0 - Bad Request</title>
<style type="text/css">
<!--
body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;background:#CBE1EF;}
code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;}
.config_source code{font-size:.8em;color:#000000;}
pre{margin:0;font-size:1.4em;word-wrap:break-word;}
ul,ol{margin:10px 0 10px 40px;}
ul.first,ol.first{margin-top:5px;}
fieldset{padding:0 15px 10px 15px;}
.summary-container fieldset{padding-bottom:5px;margin-top:4px;}
legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;}
legend{color:#333333;padding:4px 15px 4px 10px;margin:4px 0 8px -12px;_margin-top:0px;
border-top:1px solid #EDEDED;border-left:1px solid #EDEDED;border-right:1px solid #969696;
border-bottom:1px solid #969696;background:#E7ECF0;font-weight:bold;font-size:1em;}
a:link,a:visited{color:#007EFF;font-weight:bold;}
a:hover{text-decoration:none;}
h1{font-size:2.4em;margin:0;color:#FFF;}
h2{font-size:1.7em;margin:0;color:#CC0000;}
h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;}
h4{font-size:1.2em;margin:10px 0 5px 0;
}#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS",Verdana,sans-serif;
color:#FFF;background-color:#5C87B2;
}#content{margin:0 0 0 2%;position:relative;}
.summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}
.config_source{background:#fff5c4;}
.content-container p{margin:0 0 10px 0;
}#details-left{width:35%;float:left;margin-right:2%;
}#details-right{width:63%;float:left;overflow:hidden;
}#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF;
background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal;
font-size:1em;color:#FFF;text-align:right;
}#server_version p{margin:5px 0;}
table{margin:4px 0 4px 0;width:100%;border:none;}
td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:bold;border:none;}
th{width:30%;text-align:right;padding-right:2%;font-weight:normal;}
thead th{background-color:#ebebeb;width:25%;
}#details-right th{width:20%;}
table tr.alt td,table tr.alt th{background-color:#ebebeb;}
.highlight-code{color:#CC0000;font-weight:bold;font-style:italic;}
.clear{clear:both;}
.preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;}
-->
</style>
</head>
<body>
<div id="header"><h1>Server Error in Application "DEFAULT WEB SITE/MYAPP"</h1></div>
<div id="server_version"><p>Internet information Services 7.5</p></div>
<div id="content">
<div>
<fieldset><legend>Error Summary</legend>
<h2>HTTP Error 400.0 - Bad Request</h2>
<h3>Bad Request</h3>
</fieldset>
</div>
<div>
<fieldset><legend>Detailed Error information</legend>
<div id="details-left">
<table border="0" cellpadding="0" cellspacing="0">
<tr><th>Module</th><td>ManagedPipelineHandler</td></tr>
<tr><th>Notification</th><td>ExecuteRequestHandler</td></tr>
<tr><th>Handler</th><td>System.Web.Http.WebHost.HttpControllerHandler</td></tr>
<tr><th>Error Code</th><td>0x00000000</td></tr>
</table>
</div>
<div id="details-right">
<table border="0" cellpadding="0" cellspacing="0">
<tr><th>Requested URL</th><td>http://localhost:80/myapp/service/link</td></tr>
<tr><th>Physical Path</th><td>C:\workspace\myapp\service\link</td></tr>
<tr><th>logon Method</th><td>Anonymous</td></tr>
<tr><th>logon User</th><td>Anonymous</td></tr>
</table>
<div></div>
</div>
</fieldset>
</div>
<div>
<fieldset><legend>Most likely causes:</legend>
<ul> <li></li> </ul>
</fieldset>
</div>
<div>
<fieldset><legend>Things you can try:</legend>
<ul> <li>Create a tracing rule to track Failed requests for this HTTP status code. For more information about creating a tracing rule for Failed requests,click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>
</fieldset>
</div>
<div>
<fieldset><legend>Links and More information</legend>
The request Could not be understood by the server due to malformed Syntax.
<p><a href="http://go.microsoft.com/fwlink/?LinkID=62293&IIS70Error=400,0x00000000,7601">View more information »</a></p>
<p>Microsoft KNowledge Base Articles:</p>
<ul><li></li></ul>
</fieldset>
</div>
</div>
</body>
</html>
我试图设置TrySkipIisCustomErrors = True有很大的希望,但没有运气.有任何想法吗？赞赏.谢谢.
解决方法
<configuration> <system.webServer> <httpErrors existingResponse="Passthrough" /> </system.webServer> </configuration>
asp.net – .NET Web API HttpResponseMessage模式？
public HttpResponseMessage Get(string id)
{
var app = apps.Single(c => c.Id == id);
return new HttpResponseMessage(HttpStatusCode.OK)
{
Content = new ObjectContent<object>(app,Configuration.Formatters.JsonFormatter)
};
}
要么
public Application Get(string id)
{
return apps.Single(c => c.Id == id);
}
我的问题是“正确”的方式？ #2要短得多但是#1更好或#2自动做#1#？
解决方法
两种情况下的响应都是相同的(HttpResponseMessage).
HttpResponseMessage允许您使用HTTP协议(例如,通过Headers属性)并统一您的返回类型.
返回CLR类型可以更具可读性,但是您可以放松使用不同状态代码返回不同类型的灵活性,除非您使用动态或对象来抵消返回特定类型的目的.
就个人而言,我更喜欢使用IHttpActionResult(在v2中添加)并在控制器操作上为预期的返回类型指定ResponseTypeAttribute以提高可读性.
[HttpGet]
[ResponseType(typeof(Portfolio))]
public IHttpActionResult GetPortfolio([FromUri] long id)
{
// get portfolio
return Ok(portfolio);
}
您可以使用默认的IHttpActionResult实现轻松地操作响应消息(以RESTful方式)(请参阅上面的OkResult).避免自己构造HttpResponseMessage也可以保持代码清洁. Here是关于IHttpActionResult的官方文章,here是关于HttpResponseMessage和IHttpActionResult的有趣的SO对话.
关于asp.net – MVC 4 Web API Action返回：类型vs HttpResponseMessage和mvc actionresult返回值类型的问题就给大家分享到这里，感谢你花时间阅读本站内容，更多关于.net Web API 2,return HttpResponseMessage with ObjectContent、asp.net core WebApi 返回 HttpResponseMessage、ASP.NET Web Api HttpResponseException 400(错误请求)被IIS劫持、asp.net – .NET Web API HttpResponseMessage模式？等相关知识的信息别忘了在本站进行查找喔。
本文标签：
