Comments on: Web Service Interoperabilty Issues http://blog.dynatrace.com/2008/09/09/web-service-interoperabilty-issues/ dynaTrace Blog on Performance, Scalabilty and Architecture - Java and .NET Application Performance Management Tue, 16 Mar 2010 03:44:20 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Zyrex http://blog.dynatrace.com/2008/09/09/web-service-interoperabilty-issues/comment-page-1/#comment-189 Zyrex Mon, 27 Oct 2008 08:29:50 +0000 http://dynatrace.wordpress.com/?p=184#comment-189 When i check with my PC its send TCP traffic to IP called 10.0.5.12 in remote port 40002. When i check it with sniffer software it will give below type of containt of sending packet. What will be a reason for this and how can i stop this? . I try to use several firewalls to stop this but its not worked. HTTP/1.1 501 Method+%01%00%00%00E%00%00%00%7B%05%00%00%7B%00B%00B%001%00E%00F%000%00F%00C%00%2D%006%00E%001%009%00%2D%004%00A%00E%004%00%2D%00B%002%00C%00A%00%2D%008%004%00D%007%007%006%00E%009%003%002%003%00F%00%7D%00%00%008%000%002%000%00C%00%00%000%005%001%007%000%007%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%002%00%2E%000%00%2E%008%002%00%2E%000%00%00%00%01%00%00M%00I%00C%00R%00O%00S%00O%00F%00T%00+is+not+defined+in+RFC+2068+and+is+not+supported+by+the+Servlet+API+ Date: Mon, 27 Oct 2008 08:07:33 GMT Content-Type: text/html Content-Length: 3309 Connection: close Error 501 Method+%01%00%00%00E%00%00%00%7B%05%00%00%7B%00B%00B%001%00E%00F%000%00F%00C%00%2D%006%00E%001%009%00%2D%004%00A%00E%004%00%2D%00B%002%00C%00A%00%2D%008%004%00D%007%007%006%00E%009%003%002%003%00F%00%7D%00%00%008%000%002%000%00C%00%00%000%005%001%007%000%007%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%002%00%2E%000%00%2E%008%002%00%2E%000%00%00%00%01%00%00M%00I%00C%00R%00O%00S%00O%00F%00T%00+is+not+defined+in+RFC+2068+and+is+not+supported+by+the+Servlet+API+ HTTP ERROR: 501 Method+%01%00%00%00E%00%00%00%7B%05%00%00%7B%00B%00B%001%00E%00F%000%00F%00C%00%2D%006%00E%001%009%00%2D%004%00A%00E%004%00%2D%00B%002%00C%00A%00%2D%008%004%00D%007%007%006%00E%009%003%002%003%00F%00%7D%00%00%008%000%002%000%00C%00%00%000%005%001%007%000%007%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%002%00%2E%000%00%2E%008%002%00%2E%000%00%00%00%01%00%00M%00I%00C%00R%00O%00S%00O%00F%00T%00+is+not+defined+in+RFC+2068+and+is+not+supported+by+the+Servlet+API+ RequestURI=.W.i.n.d.o.w.s. .X.P. .E.m.b.e.d.d.e.d. ...S.e.r.v.i.c.e. .P.a.c.k. .2...4.7.9...4.8.7...1.1...8.0.1...A.d.o.b.e. .F.l.a.s.h. .P.l.a.y.e.r. .A.c.t.i.v.e.X.;.A.d.o.b.e. .F.l.a.s.h. .P.l.a.y.e.r. .P.l.u.g.i.n.;.F.o.x.i.t. .R.e.a.d.e.r.;.M.i.c.r.o.s.o.f.t. .B.a.s.e. .S.m.a.r.t. .C.a.r.d. .C.r.y.p.t.o.g.r.a.p.h.i.c. .S.e.r.v.i.c.e. .P.r.o.v.i.d.e.r. .P.a.c.k.a.g.e.;.U.p.d.a.t.e. .f.o.r. .W.i.n.d.o.w.s. .X.P. .(.K.B.9.2.5.8.7.6.).;.V.N.C. .F.r.e.e. .E.d.i.t.i.o.n. .4...1...2.;.V.I.A. .R.h.i.n.e.-.F.a.m.i.l.y. .F.a.s.t.-.E.t.h.e.r.n.e.t. .A.d.a.p.t.e.r.;.Y.a.h.o.o.!. .M.e.s.s.e.n.g.e.r.;.G.e.m.P.C.T.w.i.n.;.G.o.o.g.l.e. .T.a.l.k. .(.r.e.m.o.v.e. .o.n.l.y.).;.J.a.v.a.(.T.M.). .S.E. .R.u.n.t.i.m.e. .E.n.v.i.r.o.n.m.e.n.t. .6. .U.p.d.a.t.e. .1.;.W.e.b.F.l.d.r.s. .X.P.;.M.i.c.r.o.s.o.f.t. .O.f.f.i.c.e. .E.x.c.e.l. .V.i.e.w.e.r. .2.0.0.3.;.M.i.c.r.o.s.o.f.t. .O.f.f.i.c.e. .W.o.r.d. .V.i.e.w.e.r. .2.0.0.3.;.M.i.c.r.o.s.o.f.t. .O.f.f.i.c.e. .P.o.w.e.r.P.o.i.n.t. .V.i.e.w.e.r. .2.0.0.3.;.O.p.e.r.a. .9...2.6.;.M.S.N. .M.e.s.s.e.n.g.e.r. .7...5.;.R.a.l.i.n.k. .W.i.r.e.l.e.s.s. .L.A.N. <i><a href="http://jetty.mortbay.org">Powered by Jetty://</a></i> When i check with my PC its send TCP traffic to IP called 10.0.5.12 in remote port 40002.

When i check it with sniffer software it will give below type of containt of sending packet. What will be a reason for this and how can i stop this? . I try to use several firewalls to stop this but its not worked.

HTTP/1.1 501 Method+%01%00%00%00E%00%00%00%7B%05%00%00%7B%00B%00B%001%00E%00F%000%00F%00C%00%2D%006%00E%001%009%00%2D%004%00A%00E%004%00%2D%00B%002%00C%00A%00%2D%008%004%00D%007%007%006%00E%009%003%002%003%00F%00%7D%00%00%008%000%002%000%00C%00%00%000%005%001%007%000%007%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%002%00%2E%000%00%2E%008%002%00%2E%000%00%00%00%01%00%00M%00I%00C%00R%00O%00S%00O%00F%00T%00+is+not+defined+in+RFC+2068+and+is+not+supported+by+the+Servlet+API+
Date: Mon, 27 Oct 2008 08:07:33 GMT
Content-Type: text/html
Content-Length: 3309
Connection: close

Error 501 Method+%01%00%00%00E%00%00%00%7B%05%00%00%7B%00B%00B%001%00E%00F%000%00F%00C%00%2D%006%00E%001%009%00%2D%004%00A%00E%004%00%2D%00B%002%00C%00A%00%2D%008%004%00D%007%007%006%00E%009%003%002%003%00F%00%7D%00%00%008%000%002%000%00C%00%00%000%005%001%007%000%007%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%002%00%2E%000%00%2E%008%002%00%2E%000%00%00%00%01%00%00M%00I%00C%00R%00O%00S%00O%00F%00T%00+is+not+defined+in+RFC+2068+and+is+not+supported+by+the+Servlet+API+

HTTP ERROR: 501 Method+%01%00%00%00E%00%00%00%7B%05%00%00%7B%00B%00B%001%00E%00F%000%00F%00C%00%2D%006%00E%001%009%00%2D%004%00A%00E%004%00%2D%00B%002%00C%00A%00%2D%008%004%00D%007%007%006%00E%009%003%002%003%00F%00%7D%00%00%008%000%002%000%00C%00%00%000%005%001%007%000%007%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%00W%00I%00F%00I%00%5F%00K%00I%00O%00S%00K%00%00%002%00%2E%000%00%2E%008%002%00%2E%000%00%00%00%01%00%00M%00I%00C%00R%00O%00S%00O%00F%00T%00+is+not+defined+in+RFC+2068+and+is+not+supported+by+the+Servlet+API+
RequestURI=.W.i.n.d.o.w.s. .X.P. .E.m.b.e.d.d.e.d. …S.e.r.v.i.c.e. .P.a.c.k. .2…4.7.9…4.8.7…1.1…8.0.1…A.d.o.b.e. .F.l.a.s.h. .P.l.a.y.e.r. .A.c.t.i.v.e.X.;.A.d.o.b.e. .F.l.a.s.h. .P.l.a.y.e.r. .P.l.u.g.i.n.;.F.o.x.i.t. .R.e.a.d.e.r.;.M.i.c.r.o.s.o.f.t. .B.a.s.e. .S.m.a.r.t. .C.a.r.d. .C.r.y.p.t.o.g.r.a.p.h.i.c. .S.e.r.v.i.c.e. .P.r.o.v.i.d.e.r. .P.a.c.k.a.g.e.;.U.p.d.a.t.e. .f.o.r. .W.i.n.d.o.w.s. .X.P. .(.K.B.9.2.5.8.7.6.).;.V.N.C. .F.r.e.e. .E.d.i.t.i.o.n. .4…1…2.;.V.I.A. .R.h.i.n.e.-.F.a.m.i.l.y. .F.a.s.t.-.E.t.h.e.r.n.e.t. .A.d.a.p.t.e.r.;.Y.a.h.o.o.!. .M.e.s.s.e.n.g.e.r.;.G.e.m.P.C.T.w.i.n.;.G.o.o.g.l.e. .T.a.l.k. .(.r.e.m.o.v.e. .o.n.l.y.).;.J.a.v.a.(.T.M.). .S.E. .R.u.n.t.i.m.e. .E.n.v.i.r.o.n.m.e.n.t. .6. .U.p.d.a.t.e. .1.;.W.e.b.F.l.d.r.s. .X.P.;.M.i.c.r.o.s.o.f.t. .O.f.f.i.c.e. .E.x.c.e.l. .V.i.e.w.e.r. .2.0.0.3.;.M.i.c.r.o.s.o.f.t. .O.f.f.i.c.e. .W.o.r.d. .V.i.e.w.e.r. .2.0.0.3.;.M.i.c.r.o.s.o.f.t. .O.f.f.i.c.e. .P.o.w.e.r.P.o.i.n.t. .V.i.e.w.e.r. .2.0.0.3.;.O.p.e.r.a. .9…2.6.;.M.S.N. .M.e.s.s.e.n.g.e.r. .7…5.;.R.a.l.i.n.k. .W.i.r.e.l.e.s.s. .L.A.N.
Powered by Jetty://

]]> By: Andreas Grabner http://blog.dynatrace.com/2008/09/09/web-service-interoperabilty-issues/comment-page-1/#comment-29 Andreas Grabner Mon, 13 Oct 2008 19:18:32 +0000 http://dynatrace.wordpress.com/?p=184#comment-29 You are right. I should not blame SOAP in general for this issue - neither should it be HTTP. It is the SOAP/HTTP Stack Implementation that are still not a 100% interopable. As a "user" of such frameworks I expected to connect to any remote web service without having any major issues. Thanks for your comment You are right. I should not blame SOAP in general for this issue – neither should it be HTTP.
It is the SOAP/HTTP Stack Implementation that are still not a 100% interopable. As a “user” of such frameworks I expected to connect to any remote web service without having any major issues.

Thanks for your comment

]]> By: Yaron Naveh http://blog.dynatrace.com/2008/09/09/web-service-interoperabilty-issues/comment-page-1/#comment-26 Yaron Naveh Sun, 12 Oct 2008 23:09:44 +0000 http://dynatrace.wordpress.com/?p=184#comment-26 One would definitely expect these to be problems of the past. However note that SOAP is not to be blamed here - it's an HTTP issue - can also happen with REST or any regular web request. One would definitely expect these to be problems of the past. However note that SOAP is not to be blamed here – it’s an HTTP issue – can also happen with REST or any regular web request.

]]>