Uqload and Vidmoly Extractors Fix #2478
Open
+38
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request: Uqload Extractor - Fix errors, Add New Domains and Update to Latest API
Summary
Updated Uqload extractor to support additional domains and modernized implementation to match current Cloudstream ExtractorAPI standards.
Changes
1. New Domain Support
Added support for two additional Uqload mirror domains:
Uqloadcx- https://uqload.cxUqloadbz- https://uqload.bz2. API Signature Update
Updated
getUrl()method signature to match current ExtractorAPI specification:Before:
After:
3. Return Pattern Modernization
Changed from returning a list to using callback pattern:
Before:
After:
callback.invoke( newExtractorLink( source = name, name = name, url = link ) { this.referer = "$mainUrl/" } )4. Regex Pattern Fix
Corrected regex pattern to properly match Uqload's JavaScript structure:
Before:
sources:.\\[(.*?)\\]After:
sources:.\["(.*?)"\]The new pattern correctly captures URLs from arrays like:
sources: ["https://..."]5. Referer Standardization
Changed referer from dynamic
urlto consistent"$mainUrl/"for better compatibility.Technical Details
SubtitleFile,USER_AGENT,newSubtitleFile(prepared for future subtitle support)Testing
Notes
The original comment about
ERROR_CODE_PARSING_CONTAINER_UNSUPPORTED (3003)has been preserved, as this error occurs when the server returns"error_nofile"response, which is expected behavior for invalid/expired links.Disclaimer: The generation of this PR was AI assisted, however the code is 100% human.