this problem - whatever it may be - has nothing to do with okhttputils2.
my apps at the play store use okhttputils. i test on devices running android 5, 8 and 10. at the very least it
is in my interest to take note of any posting in the forum dealing with problems concerning
httputils, especially as relates to android 10. i prefer to learn about someting that might bite me before it
does bite me.
in this case, something did not sound right, so i engaged. i think it is pretty clear at this point that httputils is
not involved. i say that because i have queried the url provided using:
1) okhttuptils with b4a under android 5, 8 and 10,
2) windows 10 with the latest chrome browser,
3) curl under a unix variant which is not running the java net library (the library that okhttupils is the front end for).
they all report the same response: code 200 (ok), and a very small reponse payload consisting of the
BOM 3-byte signature.
clearly, if 2 out of the 3 systems are not running okhttupils and they get the same response as a system that is
using okhttutils, okhttputils is not odd man out.
the query's url appears to be valid. that is, the server answers requests.
the actual get parameters may or may not be valid. depending on how the server is configured, it may or
may not report an error. sometimes, the less said, the better. in the old days, we would send such
requests to /dev/null (after logging, of course). if you tell a bad guy he's sent something illegal and where
he made the mistake, he'll just fiddle with the request and try again. if you say nothing, he'll probably move on.
a less security-minded server might supply more information than it should, thinking it was being helpful.
this is why some servers do not respond to pings.
so, the url provided was an sql insert statement, which should have returned an OK (assuming it was OK).
an insert statement isn't expected to return much.
so i decided to try 3 things:
1) i simply queried the server (on port 8080) with no parameters. please see the error message below.
2) i made up a dummy sql select query using the same table that was referenced in the url.
3) i made up a dummy sql select query using an invented table (presumably invented. i invented it, but it
may have actually existed)
instead of:
Code:
insert into requisicoesronda ...
i did:
Code:
select * from requisicoesronda
and later:
the response? for what should be legal queries: status 200 (OK) and the 3 bytes (which don't mean OK, btw).
in other words, the same response either way.
for the query referencing a non-existent table harry, i got:
"SELECT * FROM harry\nTable 'condormobile.harry' doesn't exist"
so, if you put no parameters or you put bad parameters, you get a legitimate error message
(which tells me a lot about the server, more than it should have. had i been a hacker, knowing that i was
dealing with a windows box would have saved me a lot of trouble.)
but if you put what should be valid parameters, you get nothing (except status 200 and the BOM signature). so the issue is elsewhere, nothing to do with
httputils.
