Mike's sudden inspirations - WEB

WebSockets Handshake non HTTP conforming?

nospam@example.com (Mike) — Mon, 10 May 2010 10:16:00 +0200

Update:

Just found a revelatory discussion. The summary of Bjoern Hoehrmann is especially interesting with regards to that topic.

While skimming through the new HTML5 WebSocket draft, I noticed the following exemplar HTTP message demonstrating the client message of a WebSocket handshake:


        GET /demo HTTP/1.1
        Host: example.com
        Connection: Upgrade
        Sec-WebSocket-Key2: 12998 5 Y3 1  .P00
        Sec-WebSocket-Protocol: sample
        Upgrade: WebSocket
        Sec-WebSocket-Key1: 4 @1  46546xW%0l 1 5
        Origin: http://example.com

        ^n:ds[4U

To me this looks non conforming to the HTTP spec due to the lack of an indicator that the request contains a message body.

Quoting the 4th paragraph of section 4.3 of RFC2616:

The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field in the request's message-headers. A message-body MUST NOT be included in a request if the specification of the request method (section 5.1.1) does not allow sending an entity-body in requests. A server SHOULD read and forward a message-body on any request; if the request method does not include defined semantics for an entity-body, then the message-body SHOULD be ignored when handling the request.

Huh?

New development page

nospam@example.com (Mike) — Sat, 19 May 2007 19:45:00 +0200

I've finally created the basement for a development homepage, where I'll be hosting all my projects.

Drupal serves as the CMS, and I'm pondering moving my s9y--which sucks--blog over to this site. It seems that there'd be everything I needed.

Let's see if I get the menu for the blog right...

Wishlist

nospam@example.com (Mike) — Wed, 09 May 2007 19:25:00 +0200

Yes, this gonna be my wishlist placeholder.

Thank you.

Two pitfalls in one afternoon

nospam@example.com (Mike) — Thu, 03 May 2007 17:03:00 +0200

This is not my day.

<quote url="http://dev.mysql.com/doc/refman/5.0/en/fulltext-search.html">
words that are present in more than 50% of the rows are considered common and do not match
</quote>

RTFM!

Apache MultiViews are evil

nospam@example.com (Mike) — Thu, 03 May 2007 15:49:00 +0200

Suppose you've got a similar setup to:


RewriteEngine On
RewriteBase /

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule .* - [QSA,L]

RewriteRule ^network/?(\w+)?$ network.php?path=$1

Apache will expand e.g. "network/foo/bar" to "network.php/foo/bar" which won't be expanded to "network.php?f=" because it --of course-- exists (RewriteCond -f).

Evil!

Apache2 mod_domaintree version 1.3

nospam@example.com (Mike) — Fri, 27 Jan 2006 22:16:00 +0100

I just released mod_domaintree-1.3 on freshmeat.

It'll take some time to appear, though.

The code has been cleaned up a lot and a host name to directory cache (per server/process) has been added.

Enable the cache by setting DomainTreeCache to a reasonable high number, like the amount of different domains being hosted.

Drop me a mail if you like it!

Update: overflow:auto in Mozilla

nospam@example.com (Mike) — Thu, 05 Aug 2004 14:28:58 +0200

If you want the page to scroll when the scrolling-enabled DIV has nothing to scroll you'll have to wrap the contents of the scrollMe function into the following if statement:


function scrollMe(event)
{
    if (event.currentTarget.scrollHeight > 
        event.currentTarget.offsetHeight) {
        // ...
    }
}

Have fun!

Scrollable overflow:auto Elements in Mozilla

nospam@example.com (Mike) — Mon, 02 Aug 2004 12:23:00 +0200

Doing some extensive Javascript work lately, I managed to make HTML elements styled with //overflow:auto// scrollable in Mozilla.

Continue reading "Scrollable overflow:auto Elements in Mozilla"