Messages
Reply
Edit
Delete
There are three options:
1 - UrlEncoded
2 - Multi-Part form encoded
4 - No encoding
anything else - no encoding
where the last two options are pretty much the same except that nHttpPostMode = 4 sets the content type to text/xml.
Additionally, only modes 1 and 2 make sense with keys. For anything else you're posting raw POST buffers so there's no key and that code never is run.
+++ Rick ---
Rick,
In the doc's you reference mode 4 but in the case statement there are only two possible routes. If you use mode 4 the postbuffer is empty (maybe you intended this).
Furthermore, the default is nhttppostmode = 1 which will urlencode strings (no matter what). The receiver of the post may not like this though and in my case is breaking an integration with SKIPJACK for cc processing in their 'advanced processor' mode (annoying).
So, my question is should I subclass addpostkey or should you be adding a new case like this?
CASETHIS.nhttppostmode = 4THIS.cPostBuffer = this.cPostBuffer + IIF(!EMPTY(this.cPostBuffer),"&","") + ; tcKey +"="+ tcValue
West Wind Technologies
Making waves on the Web