Frequent web errors in owners view

jujubee

I've been working around a pretty frustrating error since I started with SmugMug, and it's driving me crazy!

With regularity, I can go from my home page to a sub-category, then into a gallery. The gallery "loads", but no images appear. If I refresh (reload the page in the browser), the images will usually appear about 50% of the time. The other 50% of the time, I get this error:

Bad Request

Your browser sent a request that this server could not understand.
Reference #7.3514d93f.1238989688.0

Interestingly, when I get this error and I refresh again, about 100% of the time, the reload brings the gallery back!

This problem appears often when I'm moving between galleries as well.

I'm using Safari 3.2.1, though I also see this problem in Firefox 3.0.8 (for OSX)

Any ideas?

Ann McRae

Hi jujubee

Welcome! We hope you like it here!

First, viewing problems can usually be resolved by clearing your temporary internet files - try clearing cache and see if that helps.

Second, there is a known Safari bug, that is causing some SmugMug (and other internet site) users troubles. You can read more about in Onethumb's blog.

Let us know if you have any other questions! We are always happy to help.

ann

jujubee wrote:

I've been working around a pretty frustrating error since I started with SmugMug, and it's driving me crazy!

With regularity, I can go from my home page to a sub-category, then into a gallery. The gallery "loads", but no images appear. If I refresh (reload the page in the browser), the images will usually appear about 50% of the time. The other 50% of the time, I get this error:

Bad Request

Your browser sent a request that this server could not understand.
Reference #7.3514d93f.1238989688.0

Interestingly, when I get this error and I refresh again, about 100% of the time, the reload brings the gallery back!

This problem appears often when I'm moving between galleries as well.

I'm using Safari 3.2.1, though I also see this problem in Firefox 3.0.8 (for OSX)

Any ideas?

jujubee

Looks like it was primarily the Safari bug. I do occasionally see the error even in Firefox, but at least it's not rearing it's ugly self every two minutes.

rainforest1155

jujubee wrote:

Looks like it was primarily the Safari bug. I do occasionally see the error even in Firefox, but at least it's not rearing it's ugly self every two minutes.

When, where and what is the specific error when you see it in Firefox? Be sure to include what exactly you did when you got the error.

Sebastian