Deprecated: Assigning the return value of new by reference is deprecated in /home/iaciro/public_html/wp-includes/cache.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /home/iaciro/public_html/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home/iaciro/public_html/wp-includes/theme.php on line 508

Deprecated: Assigning the return value of new by reference is deprecated in /home/iaciro/public_html/wp-content/plugins/wassup/wassup.php on line 671

Warning: Cannot modify header information - headers already sent by (output started at /home/iaciro/public_html/wp-includes/cache.php:36) in /home/iaciro/public_html/wp-content/plugins/wassup/wassup.php on line 639

WordPress database error: [Table './iaciro_blogdb/wp_wassup' is marked as crashed and should be repaired]
SELECT COUNT(id) FROM wp_wassup WHERE timestamp<''


Deprecated: Function eregi() is deprecated in /home/iaciro/public_html/wp-content/plugins/wassup/wassup.php on line 720

Deprecated: Function eregi() is deprecated in /home/iaciro/public_html/wp-content/plugins/wassup/wassup.php on line 721

Deprecated: Function eregi() is deprecated in /home/iaciro/public_html/wp-content/plugins/wassup/wassup.php on line 722

Deprecated: Function eregi() is deprecated in /home/iaciro/public_html/wp-content/plugins/wassup/wassup.php on line 725

Deprecated: Function eregi() is deprecated in /home/iaciro/public_html/wp-content/plugins/wassup/wassup.php on line 726

WordPress database error: [Table './iaciro_blogdb/wp_wassup' is marked as crashed and should be repaired]
SHOW COLUMNS FROM wp_wassup LIKE 'username'

WordPress database error: [Table './iaciro_blogdb/wp_wassup' is marked as crashed and should be repaired]
ALTER TABLE wp_wassup ADD COLUMN username VARCHAR( 50 ) NULL

WordPress database error: [Table './iaciro_blogdb/wp_wassup' is marked as crashed and should be repaired]
SHOW COLUMNS FROM wp_wassup LIKE 'comment_author'

WordPress database error: [Table './iaciro_blogdb/wp_wassup' is marked as crashed and should be repaired]
ALTER TABLE wp_wassup ADD COLUMN comment_author VARCHAR( 50 ) NULL

WordPress database error: [Table './iaciro_blogdb/wp_wassup' is marked as crashed and should be repaired]
show columns from wp_wassup LIKE 'referrer'

WordPress database error: [Table './iaciro_blogdb/wp_wassup' is marked as crashed and should be repaired]
show columns from wp_wassup LIKE 'searchpage'

WordPress database error: [Table './iaciro_blogdb/wp_wassup' is marked as crashed and should be repaired]
INSERT INTO wp_wassup (wassup_id, timestamp, ip, hostname, urlrequested, agent, referrer, search, searchpage, os, browser, language, screen_res, searchengine, spider, feed, username, comment_author) VALUES ('c9380f42564d3a7fecd04ce5d0633909','1511232612','54.145.117.60','ec2-54-145-117-60.compute-1.amazonaws.com','/2008/02/05/a-minor-detail-that-compromised-one-of-my-projects/','CCBot/2.0 (http://commoncrawl.org/faq/)','', '', '', 'N/A N/A', 'N/A ', '', '', '', '', '', '', '')

Andrei Iacob / A minor detail that compromised one of my projects
Skip to content

A minor detail that compromised one of my projects

Remember this?

I just found out what made it crash. It wasn’t the Russian DBMS, it was something else. A combination of lack of features from the Mozilla team’s products and lack of sleep from me.

After I convinced myself not to change the project (I was planning to do a Firefox extension), I returned to the CoW project and started rewriting almost the whole thing. But the same crash. I couldn’t explain it. Then, after some debugging (after a good night sleep), I narrowed it down to this:

Hmm.. Doesn’t really say anything, except for the major fact that the XAML i’m feeding my application is corrupt.

Then, I actually took a look at the XAML. In the actual XAML, not the one that the Sedna administration console was showing me.

Take a look:

<CANVAS name=”D1″ width=”700″ height=”455″ canvas.left=”0″ canvas.top=”0″>
<PATH width=”800″ height=”500″ stroke=”#FF125632″ canvas.left=”0″ canvas.top=”0″ data=”M 10,10 L 100,100″ name=”ln110″/>
<ELLIPSE width=”200″ height=”100″ fill=”#FF123456″ canvas.left=”100″ canvas.top=”100″ name=”ec111″/>
<RECTANGLE width=”10″ height=”10″ fill=”#FF125632″ canvas.left=”100″ canvas.top=”100″ name=”re112″/></CANVAS>

Yes, that’s right, the tags are all uppercase and the attribute names are also messed up.

Ok, so where did I get this XAML from?

I have a JavaScript that processes a xml after a xslt and then uses XMLSerializer.serializeToString (I’m doing the development in Firefox). The xslt is good, tested, etc. It must be the serializeToString method. It really is.

Quote:

This is much more convenient since XML standard itself is case-sensitive.

…..

3. XMLDocument object keeps the dom document by converting all tags to UPPERCASE

4. XMLSerializer.serializeToString returns all the tag names in UPPERCASE

Then, I ask myself. If XML is case-sensitive, then why the hell does serializeToString return all the tag names in uppercase?

Post a Comment

Your email is never published nor shared. Required fields are marked *
*
*