{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 聊天终结者 的问题《Does System.ServiceModel.ProtocolException always》','https://www.manongdao.com/q-992828.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Thats my question, I'm catching a few WCF exceptions on my client and the ProtocolException always has html code in its message.
Could I assume that will happen every time? For what I see the real good message comes in the inner exception, could I just discard the ProtocolException message and show the user the message from the inner exception?
相关问题
- How to make a .svc file write to asp.net Trace.axd
- WCF Service Using Client Certificates Requires Ano
- How to deploy python flask application in conda ba
- WCF error with net.tcp "The service endpoint faile
- WCF Service Reference Support Files Not Updating
No, it doesn't always contain HTML in the message. Generally if there is HTML it's because the server your talking with (or through) hasn't understood (or blocked) the request, and has replied with an HTML explanation as to why. The message is useful for figuring out the problem.
Unfortunately that isn't the only time you'll see ProtocolExceptions, so you can't assume it will always contain HTML.