Ok, here's a new one for you... I'm having trouble with the system decoding incoming cookies.
Web services is set to decode and pass a Cookie argument to my function, and it normally comes in decoded as a nested 2-column matrix. Here's what the HTML header line looks like coming from an IE browser before it's decoded:
Cookie: Talisman=Davin/xxx
If I use an APL function to perform this same (browser-like) action, and pass it the same header, APL WS also decodes it successfully into the matrix. However, if (using my APL function) I instead pass it:
Cookie: $Version=1,Talisman=Davin/xxx
then the cookie is *not* decoded properly into a 2-column matrix. (It's just returned as-is, undecoded.)
This format (with $Version) is a valid cookie format and it is accepted by all other web sites I've tried it with. (I'm not sure why IE isn't sending it in this format in the first place.)
Therefore, APL WS needs to accept more flexible formats for cookies so that it can decode all legal things that might be passed to it.