Support SCRIPT_FILENAME (NSCGI)
Repo link on SF Summary page pointing to obsolet Bitbucket repository
Thanks a lot for reporting. The link is now pointing correctly to GitHub
Repo link on SF Summary page pointing to obsolet Bitbucket repository
There is now (since Nov 6) a change following your request in the repository: https://github.com/naviserver-project/naviserver/commit/48c541c3ac647c1f45462d3c9dd90fbfbd7f1b48 Note, that this is not the usual source location (there is currently a problem on bitbucket with their changes in the licensing model). Furthermore, this change is in the main branch, whereas your diff above is from the release/4.99 branch. There are substantial changes in the main branch (to be used in the release 5.0 of NaviServer)...
No. I just need the absolute path of the currently executing script (for CGI program).
contrary to documentation "name" option to [ns_set create] is not optional.
UTF8 input not validated
There was a large reform for handling UTF-8 in NaviServer - and in Tcl as well. Full support for UTF-8 from Tcl will be introduced by the forthcoming Tcl9. NaviServer performs peroper conversions where ever necessary (e.g. in the DB drivers). Furthermore, there is a validation support in NaviServer on the Tcl level "ns_valid_utf8" and on the C API level "Ns_Valid_UTF8()".
contrary to documentation "name" option to [ns_set create] is not optional.
Many thanks for the report. This has been fixed apparently some time ago.
Is there an application that needs this variable? According to https://www.php.net/manual/en/reserved.variables.server.php scripts executed with the CLI (such as file.php or ../file.php), SCRIPT_FILENAME will contain the relative path specified by the user, otherwise the absolute pathname (not the requested file name, but the path on the file system). Is this also your expectation?
Support SCRIPT_FILENAME (NSCGI)
ns_accesslog extendedheaders
Hi Khy, Thanks for the report, this is fixed by https://bitbucket.org/naviserver/naviserver/commits/b50875f5dea00dc1c7c00ceed77e1fbacb7a6c1f Setting the extendedheaders via configuration file was ok, we use e.g. ns_section ns/server/${server}/module/nslog { ... ns_param extendedheaders "Host X-User-Id X-Mobile_p" ... } all the best -g
ns_accesslog extendedheaders
contrary to documentation "name" option to [ns_set create] is not optional.