On 04.05.18 18:44, Ian Harding wrote:
i will look into this in the near future
Thank you! I think I'll have to keep using exec curl for the time
being...
There is an updated version of NaviServer at bitbucket, which improves
the situation by leading to a consistent behavior of https and http from
the user perspective.
One can now as well distinguish between "errors" and "timeouts" by using
try:
try {
set r [ns_http run -timeout 0.01 http://google.com/]
} trap NS_TIMEOUT {msg} {
ns_log notice TIMEOUT
}
All the best
-g
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
