Am 01.04.17 um 04:56 schrieb Iuri Sampaio:
> Evaluating XMLRPC package on OpenACS, I found an error of invalid
> command name, related to the old proc htmlencode, from AOLServer. The
> error happens deep in the source code of OACS core. I was able to "grep"
> references of htmlecode in the source c
Dear all,
While working on the encodings, i found the following issue with
NaviServer url decoding. RFC 3986 (as well as earlier RFCs) define a
path as a sequence of segments, separated by slashes "/":
path-abempty = *( "/" segment )
path-absolute = "/" [ segment-nz *( "/" segment ) ]
If there was never a ns_htmlencode, shall we post in OpenACS community
forum and Bugtracker? The fix is achieved by amending ad_proc
api_proc_link within the file
packages/acs-api-browser/tcl/acs-documentation-procs.tcl, as I wrote bellow.
ad_proc api_proc_link { proc } {
Returns a full H
Hi there,
I wonder what HTTP0 means as a result of ns_http. How do I open it? Is
it a TDOM object? Should I pass the result variable in the method call?
the following chunk of code returns page with HTTP0 assigned:
/ set url [export_vars -base
"https://graph.facebook.com/oauth/access_token";
