Yep, that bug is in the underlying www libraries. OmniWeb 2.0 has no problem with that URL. Thanks for the report! Ken