Closed Bug 281571 Opened 20 years ago Closed 19 years ago

apache warning, can't find skins/standard/global.css/body_back.gif

Categories

(Bugzilla :: User Interface, defect)

defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: altlist, Assigned: myk)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041223 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041223 Firefox/1.0


   Tue Feb  8 14:55:09 2005] [error] [client 172.16.2.1] File does not exist:    
   /usr/local/bugzilla/skins/standard/global.css/body_back.gif

This is probably a firefox issue (or user error) but I'm not clear how to track
this down.  Apache is complaining it can't find the file above, even though I
can see in global.css the url line has this:

    /* generic (begin) */
    body
    {
        background: #fff url("global/body_back.gif") repeat-x;
    }

This is with the cvs tip on 02-01-2005.  

Reproducible: Always

Steps to Reproduce:
Albert: when I checked these changes in, I forgot some of the .gif files, and 
they didn't get added for about 24 hours. Sounds like you may have taken a 
version during that time. Try updating to the latest version, of the tip 
(remember to get new files and directories too) and report back.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Hi Shane,

   I do have the the gif files.  The problem isn't missing gif files but the
wrong subdirectory.  It's looking for "global.css/*.gif" instead of
"global/*.gif".  I don't know if it's my setup, bugzilla, and/or firefox.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
ah, okay. My bad for jumping the gun. I'll leave this one for Myk to fix, then, 
since it's his patch.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Fwiw, can't reproduce with Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE;
rv:1.7.5) Gecko/20041122 Firefox/1.0.
Keywords: qawanted
Couldn't find anything referencing global.css directory and can't reproduct this
 error. Note that this file is now body-back.gif because bug 285694 happened.

Albert: Do you still see this problem? If so, could you trace referer chain to
see where this .gif is referenced from?
(In reply to comment #5)
> Couldn't find anything referencing global.css directory and can't reproduct this
>  error. Note that this file is now body-back.gif because bug 285694 happened.
> 
> Albert: Do you still see this problem? If so, could you trace referer chain to
> see where this .gif is referenced from?

It's sort of better, but still a problem.  It's now looking for
skins/standard/global/body_back.gif.  Yet I can see skins/standard/global.css
and mozilla/webtools/bugzilla/skins/standard/global.css both point to
body-back.gif (hyphenated).  I also have skins/standard/global/body-back.gif.  

So I don't know which script/process is looking for the underscore version. 
Grepping in my bugzilla directory doesn't show anything.  Nor do I know how to
track it down.  Currently running bugzilla 2.20rc1+ and apache restarted a week ago.
I'm guessing this is some caching problem as the error message doesn't even
reflect the correct name of the file. Could you clear the Cache? Does this
happen with another browser?
Ok, I think this can be closed.  I'm seeing the number of warning messages
tapering down, so I guess it must be a caching problem on the browser side.  
Thanks!
Closing per reporters previous comment. Must have been browser caching issue. I
think I have seen Firefox to use old CSS even after the file has changed. Only
way to clear it was to force reload without cache.

BTW, referer chain can be traced by looking apache request log or separate
referer log for the corresponding request that triggered the error log entry. I
don't think request log contains referer information or referer log exist by
default. I usually add referer information to request log for all web sites I
manage.
Status: NEW → RESOLVED
Closed: 20 years ago19 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.