Requested modx be added to wappalyzer

I’m working on detailed pages for apps (and soon individual websites) where you can follow MODx’ growth:

http://wappalyzer.com/detail/?app=MODx

Thanks Elbert !

While I am here, I have discussed wappalyzer on a prominent french forum and someone told me SPIP had the information directly into the header like this :



As you can see you can even find addon information (not sure that’s good for security to have rev numbers too, though).

Are there many CMSes using this method ?

@dev team : Could we add it to modx, if there is no argument against it, that is ?

Quote from: davidm at Jan 26, 2009, 12:26 AM

Thanks Elbert !

While I am here, I have discussed wappalyzer on a prominent french forum and someone told me SPIP had the information directly into the header like this :

Composed-By: SPIP 2.0.2 @ www.spip.net + cfg(1.10.5),crayons(1.1),notifications(0.4),selecteurgenerique(0.2),svn_update(0
.32),topten(0.1),autorite(0.9.2)

As you can see you can even find addon information (not sure that’s good for security to have rev numbers too, though).

Are there many CMSes using this method ?

@dev team : Could we add it to modx, if there is no argument against it, that is ?

I think we could do this and only mention that it is "modx evolution" or "modx revolution" so that hackers/crackers can see if it is a version with security issues

Quote from: davidm at Jan 26, 2009, 12:26 AM

Are there many CMSes using this method ?

I haven’t been looking at headers since the add-on doesn’t make any page requests, it scans pages after they have been loaded into the browser (I’m not sure if the headers are still available in a variable somewhere). I have heard of some applications doing this but my guess is that most of them don’t.

Sending the version numbers of every single add-on is unnecessary and just plain - uhm, not smart?

Since MODX_MEDIA_PATH = "media" is not being detected on my test pages I added my question to the getSatisfaction thread;

I am in favor of having a simple thing in default templates ( a meta tag) to base the detection on;
the MODx docs should explain its purpose clearly and explicitly state that it can be freely removed/added to any template without effects on front-end or manager performance.

This way the majority of MODx sites would get indexed by wappalyzer, and the extra security by obfuscation step can be implemented in 2 seconds by any webmaster.

i’m interested too on how to indicate which modx version is to wappalizer...