$cfg["verify-protocol"] controls whether HObfus should check if the transfer protocol is HTTP or HTTPS.
Set $cfg["verify-protocol"] to 1 to enable the checking.
$cfg["verify-protocol"]=1;
If $cfg["verify-protocol"]=1 (enabled), then HObfus checks if the transfer protocol is HTTP or HTTPS. If neither, then HObfus will not output HTML code.
Note that if you open the page locally in a file manager ( instead of a web browser ), the transfer protocol is FILE ( neither HTTP nor HTTPS ).
Set $cfg["verify-protocol"] to 0 to disable the checking.
$cfg["verify-protocol"]=0;
The default value of $cfg["verify-protocol"] is 0 (disabled).
$cfg["verify-protocol"]=0;
Can you give me an example of when I should enable $cfg["verify-protocol"]?
Suppose that you enable $cfg["verify-protocol"] for your webpage. If someone downloads the webpage onto the Desktop of their local machine and opens it locally in a browser, they will see a blank page instead of the content of the webpage. This happens because $cfg["verify-protocol"] verifies the transfer protocol when they try to open it.
$cfg["verify-protocol"] displays the content of the webpage only when the transfer protocol is either HTTP or HTTPS. Since they are opening the webpage locally, the transfer protocol is FILE, which is neither HTTP nor HTTPS. So, by enabling $cfg["verify-protocol"], you have prevented them from viewing the webpage’s content on their local machine.