Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

_CTm=xml no longer works in query string (v 25.0)

  • 5 balasan
  • 2 ada masalah ini
  • 10 paparan
  • Balasan terakhir oleh JoeMoo

more options

Normally, &_CTm=xml causes a browser to interpret incoming content as XML and display a nice interface with collapsible nodes. It just quit working.

Normally, &_CTm=xml causes a browser to interpret incoming content as XML and display a nice interface with collapsible nodes. It just quit working.

All Replies (5)

more options

I've never noticed this before. Is there an example page online that works like this?

more options

Right now, every example I can think of is behind an authenticated site. I haven't seen _CTm= documented, but it works on every computer browser I've tried it on. The only 2 parameters I've ever user are xml and xls--but I'm guessing there are more. In my experience, it *is* case sensitive--and the underscore is meaningful.

more options

I can think of a few different possibilities here:

  • The server sends plain, unstyled XML, but Firefox 25 changed how it displays unstyled XML
  • The server sends XML with a reference to a style sheet, but Firefox 25 isn't retrieving/applying the XSL for some reason
  • The server sends XML and a client-side script that normally generates a tree was broken by the upgrade
  • An extension that was prettifying the XML became disabled during the upgrade (or Firefox reset during the upgrade, removing all extensions)

Do any of those appear relevant?

more options

In your "More System Details" screen, one of your plugins is listed under the name NOTFOUND. Can you track that down and see what it is? If it's not obvious from the Add-ons page, maybe this script will help (scroll down for plugin details): https://jeffersonscher.com/res/jstest.php.

more options

Well, I was really hoping that someone on this forum would help me find the actual documentation on this feature that works with the major browsers. My tries with Google turn up too much junk. In any case creating a new profile caused both the new profile and my default profile to start working OK--so apparently some malware corrupted something. Some time when I don't have anything else to do I'll create a public page that uses this feature because it is really cool. I'll mark your response as helpful but leave it out here at least a week in case someone can actually show where it's documented.

Thanks!