Sending Crafted HTTP Request Header in Kodi

Some internet streams are only available from their website. Although the underlying protocol is HTTP streaming, you won’t able to play the media simply by opening the stream URL with Kodi. That is because the streaming server checks your User-Agent and Referer to ensure you’re accessing the stream with browser from certain website.

Sending crafted HTTP request header will allow you to bypass the restriction. Here is how….

Say you have a stream URL:

For Kodi to send a specified User-Agent and Referer, you’ll have to change the URL to something like:

Note: User-Agent string and Referer string need to be modified accordingly to reflect the browser you’re using and the site you’re on.


The modified URL won’t work if added to “Favorites” (not sure why), instead, load the URL through M3U or PLS playlist.


  1. HTTP – Kodi

2 Comments for “Sending Crafted HTTP Request Header in Kodi”




Bengt Haag


Long time ago I saw a problem like

Testing HTTP Request:
User Agent:
• Expected: “Crafted Agent”
• Found: “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36”

I have forgotten how one comes around the problem. Please explain it for me.

Leave a Reply

Your email address will not be published. Required fields are marked *

Captcha loading...