When you run oozie-setup.sh prepare-war -secure it is supposed to replace server.xml with ssl-server.xml (in the oozie-server/conf/ dir) and web.xml with ssl-web.xml (in the WAR file).
OOZIE-670 changed oozie-setup.sh to prepare the war file without calling addtowar.sh. However, the code added by OOZIE-1233 and OOZIE-1268 still delegates replacing web.xml with ssl-web.xml to addtowar.sh, which oozie-setup.sh no longer calls.
Therefore, when you try to configure Oozie for HTTPS, it will use the original web.xml file; which means that all resources are accessible from both HTTPS and HTTP.
This isn't an issue in Oozie 3.3.2 because it didn't include
OOZIE-670, so addtowar.sh was still called.