Closed
Bug 452864
Opened 16 years ago
Closed 16 years ago
Zoomify problem
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 410904
People
(Reporter: celiadurand, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 I do not know it this is a bug, but I need help to figure it out. This page works perfectly well in Explorer but it does not in Firefox. Right now I have Firefox 3. I have seen other sites with Zoomify, its Flash player and files and they work fine. I try to change the permissions and does not make any difference. The same page works perfectly on my computer/Apache server. Any ideas? Thank you, Celia Reproducible: Always Steps to Reproduce: 1. Just open page and then open same page in Explorer. 2. 3.
Comment 1•16 years ago
|
||
Sorry we can't help with site programming issues here. The flash file itself is loaded fine and that means that the flash applet itself fails to find the images.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•16 years ago
|
||
If that's the case, why then it works fine in Microsoft Explorer?
Comment 3•16 years ago
|
||
I don't know why it works with IE and why it doesn't work with Firefox. Firefox is using the embed tag while IE is using the object tag. If you kinow other pages that are working then compare both ?
Reporter | ||
Comment 4•16 years ago
|
||
I hate to keep insisting, but it also works fine in Opera. What Opera uses, the embed tag or the object tag?
Comment 5•16 years ago
|
||
>I have seen other sites with Zoomify, its Flash player and files and they work
>fine.
Why Do you don't compare the page source ?
Opera is using the object Tag, the <embed> is used by Gecko for historical reasons.
Reporter | ||
Comment 6•16 years ago
|
||
>Why Do you don't compare the page source ?<
I had and the only difference I can find is that those sites have their own IP address, most of them dedicated servers, and mine has a shared IP address. Could this be the reason? If there is a chance of this beeen the problem, I'll contact my hosting company.
I also contacted Adobe and I'm waiting for their answer.
Thank you,
Celia
Reporter | ||
Comment 7•16 years ago
|
||
After more researching and proving I found the reason for my problem with Firefox. Nothing to do with shared or non shared IPs. It's the HotLink Protection. If I disable it, Zoomify works in Firefox the way it's supposed to. You can see it at (now that the Hotlink protection has been disabled): http://www.pixelgraphs.com/gallery/zoomify/summer_coleus.html The things is, I would like for obvious reasons to have that protection enabled. And it does cause any problems in Microsoft Explorer and Opera. Is there a workaround this? It seems like what I need is to be able to call the Flash engine used by Zoomify without using the <embed> tag. Any ideas? Thank you, Celia
Reporter | ||
Comment 8•16 years ago
|
||
Please see this post: http://forums.mozillazine.org/viewtopic.php?f=25&t=663910 from jscher2000: Firefox is retrieving the files, but they are coming back as web pages, not images. The usual reason for this is server-side "hotlink protection" that requires a matching HTTP_REFERER string in the request. The ActiveX version of the Flash player sends the address of the host page, but the plugin version used in Firefox does not. If that is the issue here, the following might be relevant: http_referer request not being sent with embedded flash (Bugs Forum) Why can't mozilla read this site? (another awardspace site) Flash slideshow stops after upgrading to .8 (for Apache-based hosting that lets you create a .htaccess file, how to alter hotlink protection)
Comment 9•16 years ago
|
||
That should be in your initial bug report: "Flash doesn't send referrer"
Resolution: INVALID → DUPLICATE
Reporter | ||
Comment 10•16 years ago
|
||
Thank you. When I started this post I had no idea what a "referrer" was. I have learned a lot since then. In the meanwhile, there is a workaround changing the .htaccess file to allow for a blank referrer(2nd line) and add "L" to RewriteRule: RewriteEngine on RewriteCond %{HTTP_REFERER} !^$ RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?yoursite.com [NC] RewriteRule \.(jpg|jpeg|png|gif)$ - [NC,F,L] This solved my problem for the time being.
You need to log in
before you can comment on or make changes to this bug.
Description
•