[Mono-list] Mono WCF ServiceHost
r.salomons at trisal.nl
Thu Mar 29 13:04:21 UTC 2012
I will keep replying to my own posts to :)
I have the feeling it has something to do with the fact that Sencha posts an
http method="OPTIONS" first. I can catch this, but WCF still sees it and
does not know what to do with it.
In Google Chrome i can call the WCF URL, and see the expected json output
without MONO giving an error on the serving device, but as soon as i use
Sencha, it errors.
Is that an relevant pointer?
I'm kinda' running out of options here. Is there some-one who can point me
in the right direction, or say that i should stop using mono for these
Perhaps i have not said it before, but i'm realy loving the Mono Initiative,
all other than WCF it has been great!
View this message in context: http://mono.1490590.n4.nabble.com/Mono-WCF-ServiceHost-tp4508621p4515362.html
Sent from the Mono - General mailing list archive at Nabble.com.
More information about the Mono-list