Opened 11 years ago

Closed 11 years ago

#2808 closed defect (invalid)

https protocol with parameters as input failed

Reported by: ebaynaud Owned by:
Priority: normal Component: undetermined
Version: git-master Keywords: https
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Issue with parameters when using HTTPS source. Using unsecure HTTP works well. And using HTTPS without parameters works as well.

How to reproduce:

% ffmpeg -i "https://d3qcr8gwcxn3c1.cloudfront.net/encoded/en/0_180.mp4?Expires=1378035086&Signature=S36da20XZSIneWru-1GYkTJ0kSb34ll7oTjClyyj0bEQYYyC93Cqsk26s44Khtt0DEFdJUOSaUZ28FoXp5cW~PDJUpiyRLEYouG5AFZnlrROTOI8d8K5DPvHf-1AzJb-zd~pfqx8m94K4YYFkiDCWDA82gqQYzRTGs4mpX-hCQQ_&Key-Pair-Id=APKAJQ6E3EVY3OVM4M6Q" o.mp4

It fails:

ffmpeg version 2.0 Copyright (c) 2000-2013 the FFmpeg developers
  built on Jul 25 2013 12:06:05 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  configuration: --extra-cflags=-fPIC --enable-nonfree --enable-openssl --enable-static --enable-shared --enable-gpl --enable-version3 --enable-pthreads --disable-ffplay --disable-ffserver --enable-postproc --enable-libfaac --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libmp3lame --enable-libvorbis --enable-libtheora --enable-libx264 --enable-libspeex --enable-libxvid --enable-x11grab --prefix=/usr
  libavutil      52. 38.100 / 52. 38.100
  libavcodec     55. 18.102 / 55. 18.102
  libavformat    55. 12.100 / 55. 12.100
  libavdevice    55.  3.100 / 55.  3.100
  libavfilter     3. 79.101 /  3. 79.101
  libswscale      2.  3.100 /  2.  3.100
  libswresample   0. 17.102 /  0. 17.102
  libpostproc    52.  3.100 / 52.  3.100
[https @ 0x258d4e0] HTTP error 403 Forbidden
https://d3qcr8gwcxn3c1.cloudfront.net/encoded/en/0_180.mp4?Expires=1378035086&Signature=S36da20XZSIneWru-1GYkTJ0kSb34ll7oTjClyyj0bEQYYyC93Cqsk26s44Khtt0DEFdJUOSaUZ28FoXp5cW~PDJUpiyRLEYouG5AFZnlrROTOI8d8K5DPvHf-1AzJb-zd~pfqx8m94K4YYFkiDCWDA82gqQYzRTGs4mpX-hCQQ_&Key-Pair-Id=APKAJQ6E3EVY3OVM4M6Q: Input/output error

Notice that this one work (same with HTTPS instead of HTTP):

ffmpeg -i "http://d3qcr8gwcxn3c1.cloudfront.net/encoded/en/0_180.mp4?Expires=1378035086&Signature=S36da20XZSIneWru-1GYkTJ0kSb34ll7oTjClyyj0bEQYYyC93Cqsk26s44Khtt0DEFdJUOSaUZ28FoXp5cW~PDJUpiyRLEYouG5AFZnlrROTOI8d8K5DPvHf-1AzJb-zd~pfqx8m94K4YYFkiDCWDA82gqQYzRTGs4mpX-hCQQ_&Key-Pair-Id=APKAJQ6E3EVY3OVM4M6Q" o.mp4

And this one works as well (HTTPS without parameters):

ffmpeg -i "https://tiviziodist.s3.amazonaws.com/ffmpeg.mp4" o.mp4

Change History (4)

comment:1 by ebaynaud, 11 years ago

Version: 2.0 → git-master

comment:2 by Carl Eugen Hoyos, 11 years ago

Keywords: http parameters removed
Priority: important → normal

How do you know that the https address is supposed to work? I tried wget (and curl) and get the same 403:

$ wget "https://d3qcr8gwcxn3c1.cloudfront.net/encoded/en/0_180.mp4?Expires=1378035086&Signature=S36da20XZSIneWru-1GYkTJ0kSb34ll7oTjClyyj0bEQYYyC93Cqsk26s44Khtt0DEFdJUOSaUZ28FoXp5cW~PDJUpiyRLEYouG5AFZnlrROTOI8d8K5DPvHf-1AzJb-zd~pfqx8m94K4YYFkiDCWDA82gqQYzRTGs4mpX-hCQQ_&Key-Pair-Id=APKAJQ6E3EVY3OVM4M6Q"
--2013-07-25 18:58:50--  https://d3qcr8gwcxn3c1.cloudfront.net/encoded/en/0_180.mp4?Expires=1378035086&Signature=S36da20XZSIneWru-1GYkTJ0kSb34ll7oTjClyyj0bEQYYyC93Cqsk26s44Khtt0DEFdJUOSaUZ28FoXp5cW~PDJUpiyRLEYouG5AFZnlrROTOI8d8K5DPvHf-1AzJb-zd~pfqx8m94K4YYFkiDCWDA82gqQYzRTGs4mpX-hCQQ_&Key-Pair-Id=APKAJQ6E3EVY3OVM4M6Q
Resolving d3qcr8gwcxn3c1.cloudfront.net (d3qcr8gwcxn3c1.cloudfront.net)... 54.230.45.134, 54.240.162.212, 54.240.162.88, ...
Connecting to d3qcr8gwcxn3c1.cloudfront.net (d3qcr8gwcxn3c1.cloudfront.net)|54.230.45.134|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2013-07-25 18:58:50 ERROR 403: Forbidden.

comment:3 by ebaynaud, 11 years ago

You're right, it was a bad signature issue. You can reject the issue. Sorry.

comment:4 by Carl Eugen Hoyos, 11 years ago

Resolution: → invalid
Status: new → closed
Note: See TracTickets for help on using tickets.