Keep in mind that I'm not the original author of the OpenWebif.
You might want tot thank SpaceRat for that, I just found out.how come it only works when openwebif auth is off?
It has always been that way.Bottom line, the openwebif options do not do what they suggest (imho).
Streaming auth can only be enabled and working if there is auth enabled for the OpenWebif itself, because else there is no auth resource added to the listener at all.
The only thing wrong in OpenWebif:
The option "stream auth" should be grayed out and shown as disabled if there isn't auth enabled for the webif itself.
Do whatever you want.I'll revert the change I made for this a couple of days ago and then it'll probably work.
A plain revert will just switch back to the old error, I'm too lazy to search the bug report on it here inside this thread. Nobody seems to care ...
I gave up any hope you three will ever understand the mess you produced when you started to override plugin code inside E2 itself.
All this crap is a ticking time bomb, the next explosion will come as soon as someone uses the Dream Webif or no Webif at all ...
Actually to get rid of all bugs currently (re-)producable, you will have to create a pretty long and/or condition, taking these elements into account (all bool):
- old Webif installed
- config.plugins.Webinterface.enabled
- config.plugins.Webinterface.http.auth
- config.plugins.Webinterface.streamauth
- OpenWebif installed
- config.OpenWebif.enabled
- config.OpenWebif.auth
- config.OpenWebif.auth_for_streaming
- (config.OpenWebif.port == config.plugins.Webinterface.http.port)
Until you
- either find the proper relation between them all and add them to streamproxy and E2 internal streaming
- or just revert to the only real clean state of having the active webif on port 80 handle auth
this thread will grow and grow and grow.
In the first case it will be recreated or grow again as soon as someone comes up with another web interface ...
But don't listen to a state certified engineer, just keep ignoring me.