Found at http://trendnet.com/demo/
- TRENDnet TV-IP422W Wireless Internet Camera Server http://guest:firstname.lastname@example.org:9189
- TRENDnet TV-IP301W Wireless Advanced Day/Night Internet Camera Server w/ Audio http://guest:email@example.com:9211
- TRENDnet TV-IP201W Wireless Internet Camera Server w/ Audio http://guest:firstname.lastname@example.org:9212
- TRENDnet TV-IP110W Wireless Internet Camera Server http://guest:email@example.com:9213
- TRENDnet TV-IP212W Wireless Internet Camera Server w/ 2-Way Audio http://guest:firstname.lastname@example.org:9214
- TRENDnet TV-IP312W Wireless Day/Night Internet Camera Server w/ 2-Way Audio http://guest:email@example.com:9215
- TRENDnet TV-IP400W Wireless Advanced Pan/Tilt Internet Camera Server http://guest:firstname.lastname@example.org:9222
One more time TRENDnet guys proved they can screw any great idea. M-JPEG content sent by TV-IP422W cameras has no indication of proper MIME type. We can survive this, thanks blokes you are at least giving Content-Length value! The major problem is that IJG decoder stumbles with exception on the JPEGs: each frame is prepended by 28 byte informational header (hopefully – I will have to look into the source code to find out) messing video decoder. I hope in future TRENDnet devs will discover APPn JPEG markers or multipart/mixed content-type subheaders and find it more approprioate to put this information into these cozy places.
TV-IP301W just has a typo in multipart/mixed header:
GET /goform/video3 HTTP/1.0
Authorization: Basic Z3Vlc3Q6Z3Vlc3Q=
HTTP/1.1 200 OK
OMG!!! Response line goes after Content-Type header… There is just nothing to say about this.
By “image/mpeg” (I have not found it in MIME type reference) they mean server-pushed stream of JPEG images, by the way.
BUT! These new models TV-IP212/TV-IP212W/TV-IP312/TV-IP312W/TV-IP422/TV-IP422W are much much better than older on the product line and they are still not expensive. I believe they are going to be very popular.