Closed Bug 216210 Opened 21 years ago Closed 15 years ago

yahoo.com - hotjobs serving css as text/html and application/x-pointplus

Categories

(Tech Evangelism Graveyard :: English US, defect)

x86
All
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: timeless, Unassigned)

References

()

Details

(Keywords: top100, top500)

Warning: The stylesheet http://hotjobs.yahoo.com/ was loaded as CSS even though
its MIME type, "text/html", is not "text/css".
Warning: The stylesheet https://secure.hotjobs.com/css/public/body.css was
loaded as CSS even though its MIME type, "application/x-pointplus", is not
"text/css".
Warning: The stylesheet http://img.techweb.com/portal/styles/techweb.css was
loaded as CSS even though its MIME type, "text/plain", is not "text/css".

Warning: The stylesheet http://hotjobs.yahoo.com/ was loaded as CSS even though
its MIME type, "text/html", is not "text/css".

Warning: The stylesheet https://secure.hotjobs.com/css/public/body.css was
loaded as CSS even though its MIME type, "application/x-pointplus", is not
"text/css".

Warning: The stylesheet https://secure.hotjobs.com/css/public/text.css was
loaded as CSS even though its MIME type, "application/x-pointplus", is not
"text/css".
Blocks: 121228
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: evang500
Seems to be a problem with secure.hotjobs.com and not with the non https
hotjobs.yahoo.com.
Keywords: top500
Keywords: top100
Conforming summary to TFM item 10 at 
http://www.mozilla.org/projects/tech-evangelism/site/procedures.html#file-new
OS: Windows 98 → All
Summary: HotJobs.com is serving css as text/html and application/x-pointplus → hotjobs.com - serving css as text/html and application/x-pointplus
Whiteboard: evang500
Summary: hotjobs.com - serving css as text/html and application/x-pointplus → yahoo.com - hotjobs serving css as text/html and application/x-pointplus
fixed
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.