function getarchives_filter($where, $args)
{
	if (isset($args['year']))
	{
		$where .= ' AND YEAR(post_date) = ' . intval($args['year']);
	}
	return $where;
}
add_filter('getarchives_where', 'getarchives_filter', 10, 2);

Now the wp_get_archives() function supports a year parameter which restricts results to one particular year. Next we modify the sidebar to make use of this additional argument. Here is an example of the correct call to make:

<?php wp_get_archives('type=monthly&year=' . get_the_time('Y', reset($GLOBALS['posts'])); ?>

This code also works properly when viewing the archives of a particular year, the months outputted change to the currently viewed year.

I have changed my own sidebar code to use this:

<li><h2>Archives</h2>
        <ul>
            <li><strong>Months</strong>
            <ul>
                    <?php
                    // Use the current date when viewing a page, not the pages year
                    $year = (is_page()) ? date('Y') : get_the_time('Y', reset($GLOBALS['posts']));

                    wp_get_archives('type=monthly&limit=12&year[]=' . $year . (!is_archive() ? '&year[]=' . ($year - 1) : ''));
                    ?>
            </ul>
            </li>
            <li><strong>Years</strong>
            <ul>
                    <?php wp_get_archives('type=yearly'); ?>
            </ul>
            </li>
        </ul>
</li>

Updated 31/01/2010: Paul spotted a bug, the code used the date of the last post displayed on the page rather than the first.

        $ignore = array( 'HTTP_COOKIE' );

        foreach ( $_SERVER as $key => $value )
                if ( !in_array( $key, $ignore ) )
                        $comment["$key"] = $value;

To:

        foreach ($_SERVER as $k => $v)
        {
                if (strpos($k, 'HTTP_') === 0 && $k != 'HTTP_COOKIE')
                {
                        $comment[$k] = $v;
                }
        }

        $ignore = array( 'HTTP_COOKIE' );

        foreach ( $_SERVER as $key => $value )
                if ( !in_array( $key, $ignore ) )
                        $comment["$key"] = $value;

        $query_string = '';
        foreach ( $comment as $key => $data )
                $query_string .= $key . '=' . urlencode( stripslashes($data) ) . '&';

        $response = akismet_http_post($query_string, $akismet_api_host, '/1.1/comment-check', $akismet_api_port);

The bit that worries me is the use of $_SERVER, the only item from this array not sent is HTTP_COOKIE, fair enough. But why do you need to know the full paths to the files on my server and other server environment variables Akismet? I do not have a problem with sending data to Akismet, just not this data!

Source