Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instagram Bridge failed with error 400 #696

Closed
jinjifu opened this issue May 22, 2018 · 1 comment
Closed

Instagram Bridge failed with error 400 #696

jinjifu opened this issue May 22, 2018 · 1 comment

Comments

@jinjifu
Copy link

jinjifu commented May 22, 2018

Error message: Invalid parameters value(s)
Query string: action=display&bridge=Instagram&media_type=all&format=Atom&u=brunomars

@logmanoriginal
Copy link
Contributor

The latest master fixes your issue

infominer33 pushed a commit to web-work-tools/rss-bridge that referenced this issue Apr 17, 2020
The media_type parameter was recently replaced by media_type_u (for
user mode) and media_type_h (for hashtag mode). This was necessary
in order to add the media type 'story' only for the user mode.

"The reason for that is that RSS-Bridge supports multiple parameters
with the same name if and only if they contain the exact same value.
Here, hashtags don't have stories, so it would not be possible to
pass "story" as a parameter. This is a design mistake that I made
when I added support for hashtags."

-- RSS-Bridge@b92405f?diff=split#r28871502

However as pointed out this change breaks existing feeds as the
parameter name is no longer compatible to previous implementations.

This commit changes the implementation to provide the old media_type
parameter globally and check for invalid options on each request. If
a user uses the 'story' option in history mode the bridge returns a
client error.

references b92405f
references RSS-Bridge#694
fixes RSS-Bridge#696
fixes RSS-Bridge#699
fixes RSS-Bridge#701
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants