My favorites | Sign in
Google
          
New issue | Search
for
| Advanced search | Search tips
Issue 798: Query parameters are repeated when generating next links
6 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Oct 2008
Type-Defect
Priority-High
API-Blogger


Sign in to add a comment
 
Reported by tjohns@google.com, Sep 24, 2008
If a feed is requested with a set of query parameters, those query
parameters will be reproduced verbatim when generating next links. As a
result, if max-results or start-index is included as a query parameters,
the following error will be thrown when following the next link:

   Invalid repeating query parameteter [sic]

For example, requesting a feed with ?start-index=5 might yield the
following next link:

  
http://blog.blogspot.com/feeds/posts/default?start-index=5&start-index=1&max-results=23

This blocks use of the GData paging functionality. As a workaround, users
will need to manually repair the next link.

This affects both GData v1 and v2.
Comment 1 by bhjackson, Sep 25, 2008
Just a quick note that this also breaks the GData Objective-C client, and any desktop applications which rely on 
its functionality.
Comment 3 by nivsinger, Sep 26, 2008
Discussed here http://groups.google.com/group/bloggerDev/browse_thread/thread/9bc4f5341860c661?pli=1
Comment 4 by tjohns@google.com, Oct 01, 2008
1395260

Status: Fixed
Comment 5 by tjohns@google.com, Oct 01, 2008
This should be fixed now. If you continue to experience this, please let us
know.

Comment 6 by bhjackson, Oct 01, 2008
w00t! Thanks for the fix. However it looks like there's a new bug which was introduced either in this fix or today. 
The blog name in the feed seems to be populated with the feed address. Or at least that's how it's coming out in 
Blogo. We're pulling the same info from the feed so my guess is somewhere the values got mixed up.

Let me know if you need more info to reproduce. Thanks,

Ben
Comment 7 by bhjackson, Oct 02, 2008
Disregard my last comment. Problem found and fixed.
Comment 8 by tjohns@google.com, Oct 02, 2009
(No comment was entered for this change.)
Cc: -tjo...@google.com
Sign in to add a comment