Update popr.ts

[userness]

Credit to @EndOverdosing on vyla-entertainment

Pull Request

Description

This does @EndOverdosing's recommendation to "add an isMasterOrVod" (checkStreamType) " "Also don't detect HLS by file extension since Popr's segments use .png, check the response content for #EXTM3U instead ... And make sure Referer and Origin from stream.headers are being forwarded when proxying"

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)

Related Issues

Fixes This Discussion

Changes Made

• If a request fails or returns an empty playlist, it is marked as invalid and excluded.
• Because popr uses .png for HLS files, it checks for #EXTM3U instead of .m3u8
• Forwards Referer and Origin for Proxying

Checklist

General

• My code follows the code style of this project
• My changes generate no new warnings or errors

Provider Checklist (if adding/modifying a provider)

• Provider extends BaseProvider from @omss/framework
• Provider has a unique id and descriptive name
• Provider declares correct capabilities (movies/tv support)
• Implements getMovieSources() and/or getTVSources() correctly
• All streaming URLs use this.createProxyUrl() for proxying
• Includes proper error handling with diagnostics
• Includes appropriate headers via this.HEADERS
• Returns standardized ProviderResult format

Testing

How Has This Been Tested?

The logic was verified by comparing the TypeScript implementation against the working JavaScript reference provided by @EndOverdosing..

Performance Impact

• Potential performance concern (describe below)

Details:
An extra check was added, to prevent the user being returned dead links, but causes a slight increase in resolve time.

[EndOverdosing]

Looks good. Implementation seems solid overall.

Only thing I’d point out: in checkStreamType you’re doing { ...this.HEADERS, ...headers } for the validation request, but then those headers get merged again into proxyHeaders when calling createProxyUrl. Depending on how the proxy handles headers, that could cause duplicates or conflicts.

I’d personally would use streamHeaders directly into createProxyUrl instead of merging in this.HEADERS again. The proxy really only needs stream-specific headers like Referer and Origin, not the scraper User-Agent.

[EndOverdosing]

This would be slightly slower overall, so I recommend testing each source individually. It would make it easier to identify which source is failing and why. Adding more detailed debugging to each source may be tedious, but it would be more effective overall.

[userness]

Ok I added more debuggs

[An0n-01]

I'll take a look at this. Thank you both

[GLlgGL]

Guys dont overthink to much. You can build the proxy manually and it will work on all devices just fine with the headers applies.

const STREMIO_PROXY = "http://127.0.0.1:11470/proxy";


function toStremioProxy(hlsUrl, referer) {
const parsed = new URL(hlsUrl);
const dParam = encodeURIComponent(parsed.protocol + "//" + parsed.host);
const hUA = encodeURIComponent("User-Agent:" + PAGE_HEADERS["User-Agent"]);
const hRef = encodeURIComponent("Referer:" + referer);
return ${STREMIO_PROXY}/d=${dParam}&h=${hUA}&h=${hRef}${parsed.pathname}${parsed.search};
}

Call

url: proxifyStream(finallink),

[An0n-01]

looks good. will test it out on dev branch before merging it tho.

[An0n-01]

thank you for the PR!