[Instagram] Handle instagram.com/share/ URLs generated by the mobile app #7241
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can |
|
So I went to test this, and they seem to have reverted this feature in the last few days. The app no longer gives any /share/ URL when copying links or sharing posts. My logs still show some until last Monday. I guess we can close the PR. |
- added Sec-Fetch* headers for proper redirect - fixed formatting - restore 'guide' test - integrate in PostExtractor code
mikf
force-pushed
the
djof_fix_instagram
branch
from
2084b83 to
e6f4dcf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As of december 2024, when copying the URL of a post from the Instagram Android app (I assume it's the same on other platforms) the real URL and tracking information are wrapped into a redirect formatted like:
https://www.instagram.com/share/reel/BARSSL4rTuThe real post shortcode is not the same. Making a GET on this URL with proper Sec-Fetch headers, Instagram gives a code 302 response, with the real URL in the Location headers.
This is my first contributions, I'm not sure about the PR rules, and I'm not a python dev. Let me know if I need to make any changes. The security headers were copied from the Facebook extractor. I removed the /guide test as that instagram feature no longer exist.