Maybe if you have created a rule in 3.3, upgraded, and then opened the same rule after upgrading to 4.2 that might trick it to showing Blockly for that rule. But in a new rule you shouldn’t have Blockly as an option to select from when creating an Inline Script.
Yes and no.
First: I didn’t create a rule, I only tested with scripts directly. I want to reference later to this scripts.
Now it was getting strange (tests done in my vm):
I created a script with openhab 3.3.
If I open it now with 4.2.1, I can see HTTP section! At top of the screen, directly under the name of the script, there is the hint “application/javascript”
If I create now a new script, I can choose “Design with blockly” and in the new view, there is no HTTP section and at the top is the hint “application/javascript;version=ECMAScript-5.1”.
So there must be a difference between the scripts.
But If I create a rule and add a “Then action”, choose inline script, choose “Design with Blockly”, then there is a script window with HTTP section and “application/javascript”.
Very strange, that a new rule doesn’t behave like a new script?!
Next test:
Installled JavaScript Scripting automation, created a new script, “Design with Blockly” and now there is a HTTP section and “application/javascript” at top.
(No change for a new rule, same as above.)
This gave me the idea to test with a new rule AFTER installing JavaScript Scripting on my openhab production environment. Sry, didn’t do this before, shame on me 
And a new rule or new script has now the HTTP section. But not the existing ones, also created with 4.2.1. Very odd, but no problem!
What happens if you restore a backup of your current OH 4.2 configs that are not showing the HTTP category to this test OH that is showing the HTTP category?
If that works maybe you can just start over with a fresh install of OH 4.2 on your production OH instance.
Good idea, but no longer necessary.
Big thanks for your help!! 