in the internal libraries fold of b4j there are 2 b4xlibs relating to okhttp. whichever one you're linking to, copy it from the internal folder to your additional libraries folder. rename it (important). you are then free to modify it as you wish. just make sure to include it when you build your project. i have a modified version which uses the acceptall "feature", as well as a trap for 3xx http errors. the standard okhttputils b4xlib is still available and untouched by the modified
version. no need to add the accept_all compiler directive.
i understand what you're trying to do. i went that way first. it's even possible to have both available in the same project and to call the modified version as needed. i think it's cleaner to separate things. have a modified version separate from the regular version (obviously under a different name).
it's not a good idea to use acceptall. on the android side, google would reject any app that blindly ignores security issues. on the tri64 side, if somebody downloads a file from a bad source, there could be problems for you for having allowed it (even if you warn users and give them a choice). downloading with httutils is benign, given that the downloaded data is just inactive bytes. but you may have no control over what happens with those bytes (eg, somebody loads them into a browser). have your lawyer on retainer.
