01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
voidsyck_emitter_escape( SyckEmitter *e, char *src, long len ){ int i; for( i = 0; i < len; i++ ) { if( (src[i] < 0x20) || (0x7E < src[i]) )void syck_emit_scalar( SyckEmitter *e, char *tag, enum scalar_style force_style, int force_indent, int force_width, char keep_nl, char *str, long len )/* * Basic printable test for LATIN-1 characters. */intsyck_scan_scalar( int req_width, char *cursor, long len ) if ( ! ( cursor[i] == 0x9 || cursor[i] == 0xA || cursor[i] == 0xD || ( cursor[i] >= 0x20 && cursor[i] <= 0x7E ) ) ) { flags |= SCAN_NONPRINT; }% telnet mp.nii.ac.jp imap1 LOGIN masao XXXXXX1 SELECT INBOX1 SEARCH BEFORE "23-May-2005"1 STORE 1:8000 +FLAGS (\Deleted)1 EXPUNGE1 LOGOUT% dd if=/dev/fd0 of=/tmp/fddata.img ibs=512 count=2880 conv=sync,noerror大貫ら11)の実験では,被験者がおとり画像に興味を持って見てしまうことが観察されている。http://www.example.jp/?masaohttp://www.example.jp/?masao=Subject: Corrupted redirection in Personalized search検索履歴機能つきの検索を使用している際、Googleを経由したリダイレクトを行っているようですが、一部の QueryString付きサイトへのリンクで、別のリンク先を誘導する現象が見られます。#具体的にはQueryStringsの最後に「=」を付加するような挙動があります。結果として、まったく異なるページへ誘導され、Google検索機能が使い物になりません。検索履歴を有効にしていない場合(ログインしていない)は、きちんと動いていますので、パーソナライズ検索機能のバグではないかと思います。調査・検討のほど、よろしくお願いします。当方の環境は以下のとおりです:日本語版Windows XP, FireFox1.0.7gcc -fPIC -g -O2 -fno-defer-pop -fno-omit-frame-pointer -I. -I../.. -I../../. -I../.././ext/dl -DHAVE_DLFCN_H -DHAVE_DLOPEN -DHAVE_DLCLOSE -DHAVE_DLSYM -DHAVE_DLERROR -c dl.cIn file included from dl.c:77:callback.h: 関数 `rb_dl_callback_short_1_4_stdcall' 内:callback.h:23574: internal compiler error: in ggc_recalculate_in_use_p, at ggc-page.c:1395完全なバグ報告を送って下さい。適切ならばプリプロセス後のソースをつけてください。<URL:http://the.turbolinux.co.jp/bugzilla/> を見れば方法が書いてあります。The bug is not reproduceable, so it is likely a hardware or OS problemmake: *** [dl.o] エラー 1use URI;$url1 = URI->new("http://www.example.com/");$url2 = URI->new("../")->abs($url1);print "$url1\n";print "$url2\n";http://www.example.com/http://www.example.com/../5.2. Resolving Relative References to Absolute Form g) If the resulting buffer string still begins with one or more complete path segments of "..", then the reference is considered to be in error. Implementations may handle this error by retaining these components in the resolved path (i.e., treating them as part of the final URI), by removing them from the resolved path (i.e., discarding relative levels above the root), or by avoiding traversal of the reference.5.4.2. Abnormal Examples Although the following abnormal examples are unlikely to occur in normal practice, all URI parsers should be capable of resolving them consistently. Each example uses the same base as that above. Parsers must be careful in handling cases where there are more ".." segments in a relative-path reference than there are hierarchical levels in the base URI's path. Note that the ".." syntax cannot be used to change the authority component of a URI. "../../../g" = "http://a/g" "../../../../g" = "http://a/g"ruby 1.8.4 (2005-12-24) [i686-linux]japanese-zenkaku-regionconst unsigned char *mime_pattern[] = {Sun Oct 31 14:35:26 2004 WATANABE Hirofumi <eban@ruby-lang.org> * ext/nkf/nkf-utf8/nkf.c: add "\075?UTF-8?Q?" for Gmail.<?xml version="1.0"?><methodCall> <methodName>weblogUpdates.ping</methodName> <params> <param> <value>まさおのChangeLogメモ</value> </param> <param> <value>http://masao.jpn.org/d/</value> </param> </params></methodCall>% curl -X POST -H "Content-Type: text/xml; charset=UTF8" -d @ping.xml http://rpc.technorati.jp/rpc/ping<?xml version="1.0" encoding="UTF-8"?><methodResponse><params><param><value><struct><member><name>flerror</name><value><boolean>0</boolean></value></member><member><name>message</name><value><string>Thanks for the ping</string></value></member></struct></value></param></params></methodResponse>http://api.my.yahoo.co.jp/RPC2http://api.my.yahoo.com/RPC2http://bulkfeeds.net/rpchttp://ping.blo.gs/http://ping.bloggers.jp/rpc/http://ping.cocolog-nifty.com/xmlrpchttp://rpc.blogrolling.com/pingerhttp://rpc.technorati.com/rpc/pinghttp://rpc.technorati.jp/rpc/pinghttp://rpc.weblogs.com/RPC2http://www.blogpeople.net/servlet/weblogUpdateshttp://r.hatena.ne.jp/rpchttp://www.bloglines.com/ping10 0 * * * ./delicious.rb `date -d yesterday +%Y-%m-%d` >> delicious.yml