Comment 4 for bug 1543995

That's the wrong approach for reproducing it.
The data is getting there using the Google Search all right.
I have (from work) also a Monitoring system that is analysing the actuall HTTP Traffic on the OSI Layer and that's the one who notified me on the error.
While the results are partly correct, I noticed the that the requests (when Google Search is disabled), that the "&" signs are replaced with & which is breaking the actual URL.
Check the attached wireshark screenshot. I can send you the packet capture if you want. Don't want to expose it to the net.
These "modified" entries are actually pictures embedded in the blog entry (RDF/RSS Feed), that need to be extracted through a call to a database. Hence the ID requirement.
I suspect that the entries inside the HTML Code being tagged as images get the URL normalized somehow, converting the & into &
I also attached a screenshot from the Monitoring Tool.

PS: Was skiing ;) sorry for the late reply.