Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

(http://stream-recorder.com/forum/showthread.php?t=11027)

Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

Hi!
I want to record a rtmpstream which has geo restrictions. I want to use a simple HTTP-Proxy and configure rtmpdump to use it(I don't want to use additional software). Unfortunately rtmpdump only supports Socks4. But I found a patch which adds HTTP-Proxy support for rtmpdump 2.3: http://web.archiveorange.com/archive...cEnozCqzM5eoX7
I tried that patch on linux and it seems that it works. Now I want to compile a rtmpdump-binary for windows with this patch. But I have some problems because I have not much experience with linux and compiling binaries. It would be great if someone would compile rtmpdump with http-proxy support for windows. I couldn't find anywhere a binary. I think some other people with this issue would appreciate it too. :)

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

That patch is over a year old. I tried to hand patch the files, but I cant get it to compile, and I dont know enough C to fix it.

Code:

$ make SHARED= SYS=mingw CRYPTO=POLARSSL XLDFLAGS=-static

make[1]: Entering directory `/c/home/Steven/Desktop/test/librtmp'

gcc -Wall   -DRTMPDUMP_VERSION=\"v2.4\" -DUSE_POLARSSL  -O2    -c -o rtmp.o rtmp.c

In file included from rtmp.c:132:0:

handshake.h: In function 'InitRC4Encryption':

handshake.h:116:16: warning: variable 'digestLen' set but not used [-Wunused-but-set-variable]

rtmp.c: In function 'HandleInvoke':

rtmp.c:2396:23: error: 'RTMP_LNK' has no member named 'hostname'

rtmp.c:2396:49: error: 'RTMP_LNK' has no member named 'hostname'

rtmp.c: In function 'RTMP_ReadPacket':

rtmp.c:3155:7: warning: variable 'didAlloc' set but not used [-Wunused-but-set-variable]

make[1]: *** [rtmp.o] Error 1

make[1]: Leaving directory `/c/home/Steven/Desktop/test/librtmp'

make: *** [librtmp/librtmp.a] Error 2



.

I put my efforts at
github.com/downloads/svnpenn/rtmpdump/rtmpdump-HTTP-proxy.7z

if you want to check it out.

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

It seems that you used the source from RTMPdump 2.4. But I think that patch should work with an older version. Can you try to apply the patch on rtmpdump 2.3? A big thanks for your efforts :)

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

There have been significant changes since 2.3

I am not going to do that.

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

if you change the hostname to server.host on the erring line then it should compile properly.

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

You can put rtmpdump2.4 compiled with support for HTTP-Proxy?
thanks

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

I found an other way: I managed to create a local Socks Proxy and to chain it with a HTTP-Proxy, works fine too

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

Quote:

Originally Posted by Sk1px (Post 40189)

I found an other way: I managed to create a local Socks Proxy and to chain it with a HTTP-Proxy, works fine too

you mentioned in your first post that you don't wanna use additional software otherwise i would have suggested chaining proxies earlier. anyway which software your are using currently?

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

Quote:

Originally Posted by chap

You can put rtmpdump2.4 compiled with support for HTTP-Proxy?

I created a branch at

github.com/svnpenn/rtmpdump/tree/http-proxy

It compiles, but I dont have time to upload a build right now.

Re: Compile RTMPdump for Windows with HTTP-Proxy support by applying a patch

Yes, I want still manage it without additional software otherwise I wouldn't ask. But I'm also satisfied with this way. I managed it by using Charles Webdebugging proxy. It's very userfriendly but it is not freeware. Somehow it should be also possible with 'Socks via Http' but it's more complicated.