WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 8 years ago

#2529 closed defect (bug) (invalid)

moderation.php is served with wrong mime type(?)

Reported by: Reuben Owned by:
Milestone: Priority: normal
Severity: major Version: 2.0.1
Component: Administration Keywords: bg|reporter-feedback
Focuses: Cc:

Description

This is undoubtedly something to do with my server configuration -- but nevertheless it causes nasty behaviour.

When I click manage/awaiting moderation, I get different behaviour depending on the browser:
a) Firefox - craps out, opens an infinite an ever increasing number of tabs
b) Konqueror - "An error occurred while loading http://myblog.com/wp-admin/moderation.php:
Connection to host myblog.com is broken."

Basically wordpress is somehow serving moderation.php as a file to be downloaded.

The mozilla folks suspect a funky mime type.

https://bugzilla.mozilla.org/show_bug.cgi?id=328237

Change History (3)

comment:1 davidhouse8 years ago

It's not a funky mime type, it's that we're not sending a mime type at all. This is normal as it would be annoying to stick header('Content-Type: ...') at the top of every PHP file.

Firefox's sniffing is obviously failing. My guess as to why that is is because of a weird comment you've got sitting in the mod queue, which is weirding up fx's sniffing process.

comment:2 westi8 years ago

  • Keywords bg|reporter-feedback added

moderation.php does return a Content-Type. It pulls in admin-header.php which returns the Content-Type for it:

@header('Content-type: ' . get_option('html_type') . '; charset=' . get_option('blog_charset'));

It works fine in firefox for me.

This sounds to me more like a server configuration issue.

What server setup do you have?

Can you capture the returned headers using something like the LiveHTTPHeaders firefox plugin.

comment:3 davidhouse8 years ago

  • Resolution set to invalid
  • Status changed from new to closed

There's a dump of the headers in his mozilla.org report, but there's no Content-Type among them. And yes, you're right, westi, there should be one. Try removing the '@' from the beginning of the header() call and see if you're getting an error.

Seeing as no-one can replicate and it's likely to be a server configuration problem, I'm closing. Reopen if you have evidence that WordPress is at fault.

Note: See TracTickets for help on using tickets.