Comments on: 100% Apache-Compliant REQUEST_URI for IIS and Windows! http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/ Connecting Ideas Sun, 08 Nov 2009 03:11:16 +0000 http://wordpress.org/?v=2.8.5 hourly 1 By: Bram http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-453207 Bram Mon, 26 Oct 2009 16:12:05 +0000 http://neosmart.net/blog/archives/291#comment-453207 Works like a charm !!! only included the .inc file, and all was good. nice to see 3 year old fixes still work on that F*ck*** they call IIS. why would you wanna rus IIS in the first place? Thanks again verry, verry much... kept me from rewritng the naviagtion of my site. saves me at least a day !!! Works like a charm !!!

only included the .inc file, and all was good.

nice to see 3 year old fixes still work on that F*ck*** they call IIS.
why would you wanna rus IIS in the first place?

Thanks again verry, verry much… kept me from rewritng the naviagtion of my site. saves me at least a day !!!

]]> By: jmbataller http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-447668 jmbataller Fri, 18 Sep 2009 17:08:31 +0000 http://neosmart.net/blog/archives/291#comment-447668 Good job!!! Works perfectly. Good job!!! Works perfectly.

]]> By: PHP Application Tools Developer should know | Skyje http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-304885 PHP Application Tools Developer should know | Skyje Thu, 20 Nov 2008 13:02:22 +0000 http://neosmart.net/blog/archives/291#comment-304885 [...] 100% Apache-Compliant REQUEST_URI for IIS and Windows! “REQUEST_URI for Windows is a must-install for absolutely anyone that uses IIS & PHP, no matter what software you run. It’s free, it’s one-hundred percent compatible with Apache’s own REQUEST_URI, and best of all, it’s guaranteed to work no matter what. REQUEST_URI for Windows gets whatever the user entered into the address bar - period. Nothing more, nothing less. And of course, you never have to modify a single script to make them work, this does all the work for you.” [Article/tutorial dated 11/17/2006, by The Neosmart Files. Hat tip: Sally Nordquist via Wise-Women Discussion List.] [...] [...] 100% Apache-Compliant REQUEST_URI for IIS and Windows! “REQUEST_URI for Windows is a must-install for absolutely anyone that uses IIS & PHP, no matter what software you run. It’s free, it’s one-hundred percent compatible with Apache’s own REQUEST_URI, and best of all, it’s guaranteed to work no matter what. REQUEST_URI for Windows gets whatever the user entered into the address bar – period. Nothing more, nothing less. And of course, you never have to modify a single script to make them work, this does all the work for you.” [Article/tutorial dated 11/17/2006, by The Neosmart Files. Hat tip: Sally Nordquist via Wise-Women Discussion List.] [...]

]]> By: AWSOM.org = Artist Website Setup Options Markup » Blog Archive » Further Information For Windows IIS users and Pixgallery http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-94686 AWSOM.org = Artist Website Setup Options Markup » Blog Archive » Further Information For Windows IIS users and Pixgallery Mon, 28 Jan 2008 16:50:32 +0000 http://neosmart.net/blog/archives/291#comment-94686 [...] the following webpage for information on a fix that is needed to fully support this Apache feature: http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/. It appears that the use of certain standard Server variables is not followed under the standard [...] [...] the following webpage for information on a fix that is needed to fully support this Apache feature: http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/. It appears that the use of certain standard Server variables is not followed under the standard [...]

]]> By: IIS hates REQUEST_URI and Simple PHP Flat-File Call : Carbon http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-18152 IIS hates REQUEST_URI and Simple PHP Flat-File Call : Carbon Wed, 09 May 2007 18:30:25 +0000 http://neosmart.net/blog/archives/291#comment-18152 [...] The first is the discovery of an IIS bug which does not serve the PHP-standard (and Apache-compliant) $_SERVER[”REQUEST_URI”] request thereby making many of our cookies useless. But I found a fix at The NeoSmart Files. [...] [...] The first is the discovery of an IIS bug which does not serve the PHP-standard (and Apache-compliant) $_SERVER[”REQUEST_URI”] request thereby making many of our cookies useless. But I found a fix at The NeoSmart Files. [...]

]]> By: Forum of the spiders and crawlers tracking script CrawlTrack / login to blank page. http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-15451 Forum of the spiders and crawlers tracking script CrawlTrack / login to blank page. Fri, 06 Apr 2007 21:06:14 +0000 http://neosmart.net/blog/archives/291#comment-15451 [...] and in your case it didn't work (link to your Windows system)You will find some information here:http://neosmart.net/blog/2006/100-apach … d-windows/5) For the sure, I will correct it.Jean-Denis CrawlTrack developper En ligne [...] [...] and in your case it didn’t work (link to your Windows system)You will find some information here:http://neosmart.net/blog/2006/100-apach … d-windows/5) For the sure, I will correct it.Jean-Denis CrawlTrack developper En ligne [...]

]]> By: Download Request_URI for IIS 1.0 - NeoSmart Technologies http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-14831 Download Request_URI for IIS 1.0 - NeoSmart Technologies Mon, 26 Mar 2007 12:51:45 +0000 http://neosmart.net/blog/archives/291#comment-14831 [...] Download Link 1: NeoSmart TechnologiesRequest_URI for IIS Documentation [...] [...] Download Link 1: NeoSmart TechnologiesRequest_URI for IIS Documentation [...]

]]> By: WebSpam raus! - .NET http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-14731 WebSpam raus! - .NET Sun, 18 Mar 2007 12:27:39 +0000 http://neosmart.net/blog/archives/291#comment-14731 [...] wenn man wollte,  … etwas umbauen … fr C:Inetpubwwwrootpage.restrictor.php , s.a. hier:http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/… oder, wenn man nicht wollte, z.B. diesen "Schnipsel" etwas [...]

]]> By: Dokeos Forum :: View topic - IIS $_SERVER['REQUEST_URI'] http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-11900 Dokeos Forum :: View topic - IIS $_SERVER['REQUEST_URI'] Wed, 24 Jan 2007 17:58:44 +0000 http://neosmart.net/blog/archives/291#comment-11900 <!--%kramer-ref-pre%-->[...] when surfing through the documents to include, in the learning path tool.Apparently, this page http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/ offers a solution which, even if not really easy to install, will work perfectly. The available [...]<!--%kramer-ref-post%--> [...] when surfing through the documents to include, in the learning path tool.Apparently, this page http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/ offers a solution which, even if not really easy to install, will work perfectly. The available [...]

]]> By: PHP: Variabili predefinite - Manual http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-10925 PHP: Variabili predefinite - Manual Mon, 08 Jan 2007 00:48:37 +0000 http://neosmart.net/blog/archives/291#comment-10925 <!--%kramer-ref-pre%-->[...] [...]<!--%kramer-ref-post%--> [...] [...]

]]> By: PHP: 定義済の変数 - Manual http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-9794 PHP: 定義済の変数 - Manual Mon, 18 Dec 2006 08:27:00 +0000 http://neosmart.net/blog/archives/291#comment-9794 <!--%kramer-ref-pre%-->[...] [...]<!--%kramer-ref-post%--> [...] [...]

]]> By: PHP: Variables prédéfinies - Manual http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-9744 PHP: Variables prédéfinies - Manual Fri, 15 Dec 2006 15:29:16 +0000 http://neosmart.net/blog/archives/291#comment-9744 <!--%kramer-ref-pre%-->[...] [...]<!--%kramer-ref-post%--> [...] [...]

]]> By: Nabble - Replacing TinyMCE with Xinha http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-9705 Nabble - Replacing TinyMCE with Xinha Thu, 14 Dec 2006 10:08:49 +0000 http://neosmart.net/blog/archives/291#comment-9705 <!--%kramer-ref-pre%-->[...] Reply to Author if( Nabble.user == 398755 ) { document.writeln('| Delete'); } | View Threaded | Link to this Message I've always wondered why WP used TinyMCE as the WYSIWYG editor. It doesn't result in the bestcode, it's not 100% xhtml compatible, it's not _that_ "tiny," and most importantly, there are better alternatives out there. I'm currently using Xinha (http://xinha.python-hosting.com/) to add WYSIWYG support to my commenting form, simply because of how many people throw in unencoded html characters that cut their post short. It looks great, can be configured to be even more minimal than TinyMCE, is compatible with all current-generation browsers AFAIK, and most importantly, by using the new rendering engine guarantees valid XHTML. Here's a link to a Xinha-rigged comment form: http://neosmart.net/blog/archives/291#comment-7324 It looks 100% natural and is very light (unlike FCKeditor), and has full theming support via CSS (I believe). It has the same exact feature that has only just been implemented in 2.1: html and WYSIWYG tabs, switchable via AJAX though. I use the pure HTML editor for writing posts, but my biggest turn-off in TinyMCE was how it completely mangled <a> tags, inserting many non-standard attributes that are absolutely unnecessary and serve no function as far as I can see but to create trouble and wreck havoc when TinyMCE is pulled (I had to rewrite all posts done with a WP 1.5 TinyMCE plugin after deleting it and switching to 2.0 - though that particular issue no longer exists in WP's TMCE, it _does_ still add non-standard & useless attributes to the <a> tags). Moreover, this would be a chance to do something we've long promised and talked about: removing the WYSIWYG from the actual WP-Core and making it a plugin. A plugin for Xinha on WordPress already exists, you may've seen it before: http://baptiste.us/plugins/xinha4wp My favorite thing about Xinha is the plugin system for the editor itself, it's much more straight-forward and *global* than TMCE's current plugin system and using this might encourage and simplify the use of editor-plugins. Xinha for WordPress ships with quite a few that are verified working 100% (I've checked them all on WP 2.1) including PHPSpell/ASpell support. It has several default plugins that make writing code and accessing the HTML tags from the WYSIWYG interface without actually switching to the HTML-view really easy as well. I'm sure this is going to irk some people off, TMCE has been there for a while and stuff, but I just think that TMCE has really outlived its purpose. It was made when the online blogging revolution along with Web 2.0 began, and it's really just sloppy work compared to some of the more professional follow-ups, whether they be Xinha or others. Just food for thought, something to consider, and it's definitely not hard seeing as the entire GPL'd plugin platform exists. Should this actually be considered, as simple as reviewing the plugin's code, trashing TMCE, and shipping WP with Xinha.... (Think of it this way: Way more people will switch to 2.1 when you tell them there's a new WYSIWYG engine that looks great, has tons of functions, and produces 100% valid XHTML!!! =P) Peace, Computer Guru NeoSmart Technologies http://neosmart.net/blog/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers if (Nabble.searchterms != null && Nabble.searchterms.length > 0) { Nabble.hilt(Nabble.searchterms, Nabble.get("nabble.msgtxt7601668")); } [...]<!--%kramer-ref-post%--> [...] Reply to Author if( Nabble.user == 398755 ) { document.writeln(’| Delete’); } | View Threaded | Link to this Message I’ve always wondered why WP used TinyMCE as the WYSIWYG editor. It doesn’t result in the bestcode, it’s not 100% xhtml compatible, it’s not _that_ "tiny," and most importantly, there are better alternatives out there. I’m currently using Xinha (http://xinha.python-hosting.com/) to add WYSIWYG support to my commenting form, simply because of how many people throw in unencoded html characters that cut their post short. It looks great, can be configured to be even more minimal than TinyMCE, is compatible with all current-generation browsers AFAIK, and most importantly, by using the new rendering engine guarantees valid XHTML. Here’s a link to a Xinha-rigged comment form: http://neosmart.net/blog/archives/291#comment-7324 It looks 100% natural and is very light (unlike FCKeditor), and has full theming support via CSS (I believe). It has the same exact feature that has only just been implemented in 2.1: html and WYSIWYG tabs, switchable via AJAX though. I use the pure HTML editor for writing posts, but my biggest turn-off in TinyMCE was how it completely mangled <a> tags, inserting many non-standard attributes that are absolutely unnecessary and serve no function as far as I can see but to create trouble and wreck havoc when TinyMCE is pulled (I had to rewrite all posts done with a WP 1.5 TinyMCE plugin after deleting it and switching to 2.0 – though that particular issue no longer exists in WP’s TMCE, it _does_ still add non-standard & useless attributes to the <a> tags). Moreover, this would be a chance to do something we’ve long promised and talked about: removing the WYSIWYG from the actual WP-Core and making it a plugin. A plugin for Xinha on WordPress already exists, you may’ve seen it before: http://baptiste.us/plugins/xinha4wp My favorite thing about Xinha is the plugin system for the editor itself, it’s much more straight-forward and *global* than TMCE’s current plugin system and using this might encourage and simplify the use of editor-plugins. Xinha for WordPress ships with quite a few that are verified working 100% (I’ve checked them all on WP 2.1) including PHPSpell/ASpell support. It has several default plugins that make writing code and accessing the HTML tags from the WYSIWYG interface without actually switching to the HTML-view really easy as well. I’m sure this is going to irk some people off, TMCE has been there for a while and stuff, but I just think that TMCE has really outlived its purpose. It was made when the online blogging revolution along with Web 2.0 began, and it’s really just sloppy work compared to some of the more professional follow-ups, whether they be Xinha or others. Just food for thought, something to consider, and it’s definitely not hard seeing as the entire GPL’d plugin platform exists. Should this actually be considered, as simple as reviewing the plugin’s code, trashing TMCE, and shipping WP with Xinha…. (Think of it this way: Way more people will switch to 2.1 when you tell them there’s a new WYSIWYG engine that looks great, has tons of functions, and produces 100% valid XHTML!!! =P) Peace, Computer Guru NeoSmart Technologies http://neosmart.net/blog/ _______________________________________________ wp-hackers mailing list wp-hackers@… http://lists.automattic.com/mailman/listinfo/wp-hackers if (Nabble.searchterms != null && Nabble.searchterms.length > 0) { Nabble.hilt(Nabble.searchterms, Nabble.get(”nabble.msgtxt7601668″)); } [...]

]]> By: PHP: Variáveis predefinidas - Manual http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-9704 PHP: Variáveis predefinidas - Manual Thu, 14 Dec 2006 08:43:04 +0000 http://neosmart.net/blog/archives/291#comment-9704 <!--%kramer-ref-pre%-->[...] [...]<!--%kramer-ref-post%--> [...] [...]

]]> By: :: View topic - REQUEST_URI http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/#comment-8389 :: View topic - REQUEST_URI Fri, 01 Dec 2006 09:27:00 +0000 http://neosmart.net/blog/archives/291#comment-8389 <!--%kramer-ref-pre%-->[...] http://neosmart.net/blog/archives/291 is there any chance of this being set up on easycgi? i would love to have url's that don't have [...]<!--%kramer-ref-post%--> [...] http://neosmart.net/blog/archives/291 is there any chance of this being set up on easycgi? i would love to have url’s that don’t have [...]

]]>