Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[databoy2k]

Hey All:

First post and trying not to rage. I've got a pair of D-Link DCS-932L's. Recently upgraded to 1.14 firmware (Revision A).

The lack of support for Chrome is beyond infuriating, since nothing that I use the cameras for requires Java. Only an idiot (or Microsoft itself) thinks that forcing users to use Internet Explorer is better for security or usability than Chrome. Please, for the love of all that is good, let Chrome users bypass the warning page.

But here's my real question. I use HTTP POST commands through a third party app to control various parts of my network, particularly these cameras. Of course, in the effort to block Chrome and its users out of spite, the cameras only allow Internet Explorer, Firefox, or Safari to send ANY command. Notwithstanding the new hatred of Chrome, there is no reason to blacklist all user agent strings except the whitelist of those three options. If you can't stand Chrome, please blacklist just it and let the rest of the world function.

Last issue though: my POST commands are getting "403:Forbidden" when I pass them using an "appropriate" user agent (despite being authenticated). Why is that? Is this some new security measure? Are there any workarounds?

Sorry for the rant, but I'm absolutely seething and am trying to remain respectful. Please help D-Link.

--Databoy2k

[FurryNutz]

Have you tried using HTTP instead of HTTPS?

We recommend using FF or IE11 has Google has made there own decisions to block some plug-ins and such in there browser. IE11 and FF is a bit more forgiving.

[databoy2k]

Thanks for the quick response. I'm using HTTP, not HTTPS.

Recommend is fine, but this is clearly not a recommending issue. This is a whitelisting issue allowing three browsers through and blocking everything else, including (I hope I'm wrong on this) raw HTTP Post commands carrying one of the whitelisted user-agent strings. That's wrong. I get not having the technical ability to code HTML5 (I assume that's the whole issue here), but this is preventing passing commands to the camera just because it isn't Firefox sending the command.

Again, I hope I'm wrong and this 403 error is something else, but it's looking like D-Link's new whitelist is preventing any other uses that aren't IE/Firefox/Safari, and that's infuriating.

[FurryNutz]

There maybe some commands that D-Link isn't allowing for security reason thus why your getting errors. I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. Ask them what is and isn't supported. We find that phone contact has better immediate results over using email.
Let us know how it goes please.