Need help from a SOAP expert

I'm using the Microsoft.Web.Services2.WebServicesClientProtocol to make web services call (we're sending auth info for each request). But I also want to send extra info along w/ each request (like client version #, etc...).

I thought doing a

WebServicesClientProtocol.RequestSoapContext.Add("keyName", "info")

would do the trick, but using ProxyTrace (lets you examine SOAP request/response w/out changing the code too much), I don't see it in the stream. Does anyone know how to do this?

Have you tried looking at the raw packets?

DoomBringer wrote:

Have you tried looking at the raw packets?

Not really. There would just be too much code that needs to be re-written & re-test, otherwise.

Minh wrote:



DoomBringer wrote: Have you tried looking at the raw packets?

Not really. There would just be too much code that needs to be re-written & re-test, otherwise.

No, I mean a packet sniffer.

I'm no expert but I've been using Dove for many years now and it's keeps me clean and fully moisturised definately reccomend it.








sorry ill get me coat

How do you send the auth-info? Do you put it in the Header of the soap message or is it part of the body/main message?

you can use WSE-filter to to add the wanted informationdata into the header.

or am i far from the scope now ?

Halvor wrote:

How do you send the auth-info? Do you put it in the Header of the soap message or is it part of the body/main message?

you can use WSE-filter to to add the wanted informationdata into the header.

or am i far from the scope now ?

We're sending the credentials by putting it into the

Microsoft.Web.Services2.SoapContext.Security.Tokens

collection, and that code is stuck in a library. But I wouldn't want to mess with the security anyway. I was hoping I could just slip a little somethin' somethin' into the XML message & pull it out at the other end without bothering too many folks.

DoomBringer wrote:

Minh wrote: DoomBringer wrote: Have you tried looking at the raw packets? Not really. There would just be too much code that needs to be re-written & re-test, otherwise.

No, I mean a packet sniffer.

ProxyTrace is pretty cool, it essentially is a packet sniffer for SOAP messages.

leeappdalecom wrote:

I'm no expert but I've been using Dove for many years now and it's keeps me clean and fully moisturised definately reccomend it.








sorry ill get me coat

You sir are a fraud. Everyone knows Ivory is 99.44% pure and is the best.

Minh wrote:



leeappdalecom wrote: I'm no expert but I've been using Dove for many years now and it's keeps me clean and fully moisturised definately reccomend it. sorry ill get me coat

You sir are a fraud. Everyone knows Ivory is 99.44% pure and is the best.

My silky smooth fully hydrated skin speaks for itself

Minh wrote:



DoomBringer wrote: Minh wrote: DoomBringer wrote: Have you tried looking at the raw packets? Not really. There would just be too much code that needs to be re-written & re-test, otherwise. No, I mean a packet sniffer.

ProxyTrace is pretty cool, it essentially is a packet sniffer for SOAP messages.

I've used things like that before, SOAP Scope I think was one of them.  But these days, I'm more interested in whats going on at the very wire level, so I use Ethereal (now called Wireshark).  Though ethereal has had a startling number of security updates...