for Chris Anderson (bizaare behavior for filtered change notification)

[Seung Chan Lim]

At firstI first formed my URL like so:

http://lite.couchbase./status32/_changes?feed=continuous&include_docs=true&filter=magic/by_attr&doc_ids=%7B%22role%22%3A%5B%22Person%22%5D%7D

and the XMLHTTPRequest would not advance after readyState of 1

Out of whim, I changed it to

http://lite.couchbase./status32/_changes?feed=continuous&include_docs=true&doc_ids=%7B%22role%22%3A%5B%22Person%22%5D%7D&filter=magic/by_attr

and the problem went away.

Curious, I reverted back to 

http://lite.couchbase./status32/_changes?feed=continuous&include_docs=true&filter=magic/by_attr&doc_ids=%7B%22role%22%3A%5B%22Person%22%5D%7D

And the initial stalling problem went away.

Absolutely nothing else in the code changed...

I just found this bizarre, but maybe it's meaningful to some transient bug??

Obviously, I can no longer reproduce this.

slim

[Jens Alfke]

Yikes! Since the problem went away after a meaningless change to the URL, maybe it had something to do with caching? Maybe WebKit had cached a bad response from the first URL, so when you changed to the second equivalent URL it sent the request again and got a better response?

—Jens

[Seung Chan Lim]

I suppose that's possible.