ID:96632
 
Resolved
Recent versions of Google Chrome have been mangling the byond:// URLs used to download games and turning the # character into %23 when passing the URL to the pager. While this is not a BYOND bug, the pager is now capable of working around this issue my recognizing some of the malformed URLs and attempting to correct the damage. If problems persist, please use a different browser until Google fixes the issue.
BYOND Version:470
Operating System:Windows XP Home
Web Browser:Chrome 5.0.375.55
Applies to:BYOND Pager
Status: Resolved (471)

This issue has been resolved.
Duplicates:id:96701, id:97741, id:97104, id:96986, id:97176, id:96990
Descriptive Problem Summary:
You cannot download anything on the website using google chrome.
Numbered Steps to Reproduce Problem:
View Byond.com with google chrome download any games host files from any hub.
Expected Results:
Download the host file or libary.
Actual Results:
Pager uses the wrong location to download from and views the user as a guest even if loged in.
Does the problem occur:Often


When does the problem NOT occur?
When I use another browser
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)

Workarounds:Use another browser Firefox works fine but IE is the best for Byond even though it sickens me to say that.

I use chrome, the downloads are working for me...
On chrome 5.0.375.55 on xp-sp3, library downloads don't work. I click on, say YourFirstWorld's "byond://Dantom.YourFirstWorld##version=4##guest"

By the time it gets to the splash screen, the #s have been escaped and it says "Could not find [thelink]"

Copy and pasting the link into the pager works, since the #s aren't escaped then.
I don't fully follow what you mean about escaping. Can you be more specific?

This probably qualifies as a Chrome bug and not a bug with our site as such, but if there's a way to work around their garbage I'll look into it.
The links looks fine within chrome. I click on it, and between then and when it hits the BYOND splash screen, the #s get escaped, so the splash screen says:

'Could not find byond://Dantom.YourFirstWorld%23%23version=4%23%23guest'
Now that I upgraded to chrome now im having the problem....
I still haven't figured out an acceptable workaround, but I will. This is most definitely a bug in Chrome, not a BYOND bug, but once I find a way to work around the issue I'll close the report.

In the meantime, Chrome users can help by reporting the bug to Google. (It really should be done by Chrome users because they can report which versions have the issue.) The bug is that when using a custom protocol (in our case, byond://) to launch an external application, Chrome is escaping hash characters (#) in URLs as %23. It may be escaping others as well. This is inappropriate and incorrect behavior that does not match what Firefox and even IE both do correctly. Chrome should be preserving the URLs as-is and passing them to the operating system unmolested.

If anyone does file a bug report, please post a link to it here so we can keep track of it.