sorry to raise this old chestnut again, but hopefully someone can throw some light on a new issue I have with authentication.
in summary, I have two separate intercoms set up to make an http request to Indigo (using the HTTPd Plugin) on certain events (door bell press, motion).
one of the intercoms works perfectly (I can use the variable change to trigger a range of actions)
the other intercom (configured identically, except with different variable names) throws up an authentication error. I would have concluded there is a difference in the way the two DoorBird intercoms are generating authentication headers (whilst the config is so far as I can tell identical, they are different generations of DoorBird intercom)...however I get the same error message even using http...makes me think there error must be mine?
- Code: Select all
HTTPd Debug AuthHandler: GET from 10.0.1.xx:xxxx for /setvar?frontdoorbell=doorbellevent
HTTPd Debug AuthHandler: Request has no Authorization header
the request works fine from a browser (once authorised).
I have a couple of thoughts I'd appreciate any comments on:-
- I assume having two different devices making requests to the same HTTPd service device shouldn't complicate authentication? Should I be able to issue this with no authentication header?
- of course all the info I need is appearing in my log in the form of the URL...it just isn't being acted upon. I assume there's no way of ignoring the authentication issue and just matching this string (similar to the Cynical Networks plugin). Given only one of the intercoms is generating the error, I could deduct which intercom has attempted communication by using the HTTPd plugin's trigger event and some conditional logic to exclude events that were properly processed (although this hack wouldn't reveal which url/sensor was involved).