S
sjellin.dovetail
Guest
Hi All, (Tried in 11.6, Unix). I am trying to convince a client to fix their lack of status code reply, but unfortunately curl -w "%{http_code}" and some other tools just decide that :00 means status 200. Funnily enough curl -i shows that the raw reply is :00. Also tried in postman and it also just decides to return 200. On the OpenEdge.net.pl log output i also see the :00 status code. The issue is that just making the call causes the 4gl to give the following error ** Invalid character in numeric input :. (76). I could catch the invalid character exception but that feels like looking for trouble. Is this something that works in 11.7 ? (I can't access the url from the 11.7 environment i have) - or is there some magic setting that can be used to override the status to 200 without a catch block ? This seems like a 200 should be almost a default if utilities like curl etc just happily return a 200 when explicitly asked to return the value.
Continue reading...
Continue reading...