Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / December 2005

Tip: Looking for answers? Try searching our database.

WSE 3.0 and MTOM issues

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Shaji Sethu - 13 Dec 2005 22:41 GMT
While creating a sample application to send and recive pictures I created a
simple web service that would allow people to send pictures and view
pictures. All worked well till I enabled MTOM on the services. Since then
everythime the client tries to connect to the service it gets the following
message "The request failed with HTTP status 415: Unsupported Media Type.".
I have looked around in newsgroups and not found any resolution. BTW the web
services is hosted inside IIS running on XP pro with SP2, have not tries if
it will work on VS 2005 inbuilt web server (had I chosen directory option
instead of web server).

For now I have decided to move on if any of you find a resolution do let me
know, if I find it will post it here.

The raw messages is below that is sent to server
"POST /VisitorDataService/VisitorService.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 2.0.50727.42)
VsDebuggerCausalityData:
uIDPo4jPn8RWmPlAjcQTkQgpUHMAAAAAX7/rVlC6HkyUzBUqLrewxBLVzD4GiL1Cips5Q4ONci0ACAAA
SOAPAction: "http://www.shajisethu.com/schemas/VisitorService/getVisitors"
Host: sethu.homedns.org
Content-Type: multipart/related; type="application/xop+xml";
boundary=--MIMEBoundary632701497681437264;
start="<0.632701497681437264@example.org>"; start-info="text/xml;
charset=utf-8"
Content-Length: 1424
Expect: 100-continue
Proxy-Connection: Keep-Alive

----MIMEBoundary632701497681437264
content-id: <0.632701497681437264@example.org>
content-type: application/xop+xml; charset=utf-8; type="text/xml;
charset=utf-8"
content-transfer-encoding: binary

http://www.shajisethu.com/schemas/VisitorService/getVisitorsurn:uuid:bd1fa634-e6
20-4649-a316-b7d64d80e71bhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/a
nonymoushttp://sethu.homedns.org/VisitorDataService/VisitorService.asmx2005-12-1
3T22:36:08Z2005-12-13T22:41:08Z

----MIMEBoundary632701497681437264--"
Tim_Mac - 23 Dec 2005 01:04 GMT
hi Shaji,
i also encountered this error in my web application. with some research, i
found out that i was missing one line from my web.config:
<soapServerProtocolFactory type="Microsoft.Web.Services3.WseProtocolFactory,
Microsoft.Web.Services3, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>

it belongs in the section:
  <system.web>
       <webServices>

once i added this, the web service worked perfectly.

hope this helps your scenario.
tim

--------------------------
blog: http://tim.mackey.ie 
Shaji Sethu - 23 Dec 2005 02:44 GMT
Tim,
I made those changes and it worked like a charm.

Thanks.

/Shaji

> hi Shaji,
> i also encountered this error in my web application. with some research, i
[quoted text clipped - 14 lines]
> --------------------------
> blog: http://tim.mackey.ie

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.