SlideShare Returns 999 Request Denied from Inside Docker Container


(Sawood Alam) #1

I have this annoying issue on my test installation on DigitalOcean where onebox is not working for SlideShare. On close inspection, I found that the onebox proxy is returning 404. Then entered inside the container to see if I can access the resource from inside.

discourse-container# curl -I http://www.slideshare.net/ibnesayeed/introducing-web-archiving-and-wsdl-research-group
HTTP/1.1 999 Request denied
Date: Mon, 05 Dec 2016 15:13:01 GMT
X-Li-Pop: prod-lva1
Content-Length: 1629
Content-Type: text/html

It returned 999 Request denied from inside the container. However, if I make the same request from the host machine running the container, the results are different.

host-machine# curl -I http://www.slideshare.net/ibnesayeed/introducing-web-archiving-and-wsdl-research-group
HTTP/1.1 200 OK
Server: nginx
Date: Mon, 05 Dec 2016 14:51:49 GMT
Content-Type: text/html; charset=utf-8
Status: 200 OK
X-Request-UUID: an/wZ/e5BTqiixp0HhjImw==
X-Content-Type-Options: nosniff
X-Bench-ID: s66484106/a39165931
X-Runtime: 0.479692
X-Frame-Options: SAMEORIGIN
X-Bench-Route: slideshow/view
X-Request-Id: 7263494862eb782405962cfd7be4cb18
Cache-Control: max-age=86400, public
X-UA-Compatible: IE=Edge,chrome=1
X-XSS-Protection: 1; mode=block
P3P: CP="OTI DSP COR CUR ADM DEV PSD IVD CONo OUR IND"
X-Content-Type-Options: nosniff
X-Varnish: 183328799
Age: 0
X-FS-UUID: 5957cc67bb638d14c099db426a2b0000
X-Li-Fabric: prod-lva1
Set-Cookie: _uv_id=1087004406; Path=/; Domain=.slideshare.net
Set-Cookie: SERVERID=r87|WEV/C|WEV/C; path=/
Set-Cookie: bcookie="v=2&497d8fba-6e9d-4c6c-850e-0f60cccefe21"; domain=.slideshare.net; Path=/; Expires=Thu, 06-Dec-2018 02:29:21 GMT
Connection: keep-alive
X-Li-Pop: prod-lva1
X-LI-UUID: WVfMZ7tjjRTAmdtCaisAAA==

Any help what could be done about it?


(Rafael dos Santos Silva) #2

Can’t repro this on my instances.


(Sawood Alam) #3

I can’t reproduce it on my local machine either, but on my DO instance it is quite consistent. I didn’t customize anything in the container’s network. I even tried restarting the container, but it didn’t help either. Now I am really clueless what else should I try.


(RĂ©gis Hanol) #4

Maybe the IP address of your droplet was previously used to “spam” slideshare with requests and they blacklisted it?


(Sawood Alam) #5

If that was the case then requests from inside the container as well as from the host, both would behave the same. However, requests made from inside the container are blocked, but those from outside are not (as illustrated in the codes above).


(RĂ©gis Hanol) #6

Nevermind, didn’t read your post properly :blush: