id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1878	NS_ERROR_MALFORMED_URI when accessing EBSCO via proxy	ajlyon	simon	"There's [http://forums.zotero.org/discussion/18789/2/ebsco-host-translators-not-working/ a report on the forums] of this error: 
{{{
[JavaScript Error: ""[Exception... ""Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIIOService.newURI]"" nsresult: ""0x804b000a (NS_ERROR_MALFORMED_URI)"" location: ""JS frame :: chrome://zotero/content/xpcom/proxy.js :: <TOP_LEVEL> :: line 316"" data: no]"" {file: ""file:///Users/ed/Library/Application%20Support/Firefox/Profiles/ife062iq.default/zotero/translators/EBSCOhost.js"" line: 0}]
}}}

My thought was that this is being caused by presence of fragment identifiers (#..) in the URLs, but that doesn't seem to be the case. I'm not sure what's happening, but it seems to me that it shouldn't be possible for translators to trigger errors like this using ordinary doGet/processDocuments calls."	defect	closed	major		ingester		fixed