BUG: NO proxy support for netcams anymore

When curl was ditched, so was the support for proxies. I can no longer connect to netcams outside my intranet!

Test case

Environment

Motion version:	3.1.19
ffmpeg version:
Shared libraries:	curl, xmlrpc, ffmpeg, mysql, postgresql
Server OS:	Debian Sarge

-- TWikiGuest - 30 Mar 2005

Follow up

Never knew it worked with cURL.

Well. Hopefully we can get it in again sometime. Guess Kit is focussing on stability for the moment. But if he or someone else will code it I support fully getting it back in Motion.

If Kit or Angel want to pick it up they can assign it to themselves. Will keep it "new" for now.

Expect this to be added in 3.2.X only.

-- KennethLavrsen - 30 Mar 2005

---

This was a surprise to me as well. This fix will take a little while, though, since the primary goal right now is stablizing the code. I basically know how to provide proxy support, just haven't thought of the most appropriate way to implement it.

-- ChristopherPrice - 31 Mar 2005

---

Status update:

After rewriting the url handling code, this should be much easier to handle. My initial thought is something in the config file like:

netcam_url proxy://example.com/http://example.com/video.cgi

It may look a little ugly, but it will work with minimal tinkering with the code. Also, no introduction of additional configuration options!

-- ChristopherPrice - 15 Apr 2005

That seems like a good proposal.

-- KennethLavrsen - 15 Apr 2005

It looks to me as if it would be fairly simple to implement this with (yet another) configuration parameter, e.g.

netcam_proxy http://proxyhostname{:proxyport}

If there is no objection to this approach, and if someone can provide me with a proxy server to test with, I can (try) to implement this in the new netcam.c code

-- BillBrack - 2 Aug 2005

---

A netcam_proxy option is probably the best way since the other syntax may not be very logical.

-- KennethLavrsen - 02 Aug 2005

Fix record

2 Aug 2005 (PDT)

I coded a patch NetcamProxyServerPatch which (hopefully) will fix this problem.

---

The patch is included in 3.2.2_snap10 and forward.

KennethLavrsen