I ported the http GET request to Twitter with a Rebol command. Rebol was chained to Fiddler as a proxy.
The url included the callback reference when passed via Rebol's http GET request
http://search.twitter.com/search.json...
It came through very clean, without trashing the response.
I have to look at wireshark to see the packets and the conversation.
That will take time.
Passing the request via chrome's navigation entry field produces failed response when rendered in the browser.
So this suggests that chrome is somehow responsible for the problem....
Thanks for your reply, I've tested it in Firefox from the beginning and it's returned the error, but now it's fine.
I ran it in Firefox and I now have the fields populated correctly.
It was blocked until I pulled Fiddler out of the proxy configuration.
Firefox indicated that it could not validate the security certificate when run through Fiddler. It would seem that Fiddler is responsible.
As much as it wasn't a flaw in your code or the browser, it is just as well to know that a proxy that is used for debugging traffic can actually be its own cause.
I will keep my eye open for the configuration that corrects the problem, and if I find it, I will pass it along.
Of the top of my head it is best not to let Fiddler decrypt and reencrypt traffic in transit unless it is necessary. Just extra overhead.
Essentially the browser was not satisfied with a "man in the middle" situation caused by Fiddler using its own unsigned certificate.
It suggests that the security rule set is actually catching certificate substitutions, and making the appropriate validation checks .
Thank you for being so quick to address the issue I put forth.
It's good to know there is a sounding board for technical issues.
: )))
The reason that the REBOL request went through is that it was not issued via https:// , and as a result did not invoke the certificate substitution by Fiddler, despite it still being the proxy for the traffic.
Just thought I would point that out.
Its official...
Fiddler was breaking the conversation.
I told it to stop intercepting and decrypting conversations and removed its certificates from the local system.
The problem cleared.
Code runs in Chrome, no problems.
Code runs in Firefox, no problems.
Thanks.
therefore it SHOULD shrink. You can't fight Africa""}