404 from GreaseMonkey when getting script -- All indications are that file exists

[H. Ryan Jones]

Hi,

I have a strange problem, that appears to be an issue with GreaseMonkey itself.  I'm getting 404s when GreaseMonkey (1.4) tries to download a script that we store in SVN.  If GreaseMonkey is uninstalled then the same Firefox browser (v. 14.0.1) can download the script just fine (as well as via curl or Chrome).  Additionally, I have tracked the problem down to an older version of the script which downloads fine and the next version which gives a 404 -- this suggests that there's something weird in the newer script that is causing the issue.  So, I did a diff through the files and don't see anything (esp. in the GreaseMonkey headers at the top) that would seem to be an issue.  I also thought that there might be a weird control character issue, but this doesn't appear to be the case (see diff below):

# V55.js has problem & V54.js doesn't, cat -A shows control characters prepended by a ^, so to get the character I grep for a carrot and the next character, then unique sort these and get the same thing from both files

$ diff <(cat -A V54.js | grep -Eo "\^." | sort -u) <(cat -A V55.js | grep -Eo "\^." | sort -u)
$

Any other ideas on how I can debug this?

Thanks for your help!
Ryan

[Anthony Lieuallen]

Are these files only available at URLs that the public can't access?  If so, can you provide the "diff -u" output of the two files?  If you copy the files to another web server (not subversion) does that help?

Ryan

--
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/greasemonkey-users/-/0OLeOhryBBcJ.
To post to this group, send email to greasemon...@googlegroups.com.
To unsubscribe from this group, send email to greasemonkey-us...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.

[H. Ryan Jones]

Thanks for those suggestions, Anthony, I hadn't thought to try putting them on another server to absolutely make sure that it's not a weirdness of SVN.  I did that and got the same problem.

It looks like a diff -u just is a different diff output.  There's quite a few changes between the two versions (I already looked over this fairly closely using vimdiff).  Unfortunately, I can't give you access to the files as they mention a lot of Amazon internal addresses.  It's probably not a big deal, but I just want to be careful.

I'll look a little more closely at the diff, but it's weird because I test these out with a local version before pushing it to SVN, and didn't see this issue for a number of version changes.

Any other ideas you have would be much appreciated.

Thanks,
Ryan

To unsubscribe from this group, send email to greasemonkey-users+unsub...@googlegroups.com.

[H. Ryan Jones]

Yay!  Okay, I figured it out after looking a little bit closer at the diff and I found that one of the files that I had in a
// @require
statement at the top had been moved to a different location (and it's old location was giving a 404).  This still does seem like it could be an improvement in GreaseMonkey because the error message didn't mention this was the problem file (rather than the script itself).

I'm going to see if I can put in a feature request to have GMonkey check for that or at least give a better debug message.

Thanks again!
Ryan

[H. Ryan Jones]

Hey Anthony,

In looking for a way to make a feature request, I saw that your name is at the beginning of the list for Authors on the main GreaseMonkey downloading page.  Is this the appropriate forum to make that request?

I can probably make a reproduction case that's public for you to use?  Also, the specific error I was seeing is:

Download Error

Error downloading URL: <URL-TO-MY-SCRIPT-REMOVED>

Server returned 404 Not Found.

The super quick-and-dirty fix would be to say something like:

A "404 Not Found" was returned when downloading <SCRIPT-URL> or one of it's required scripts.

Even better would be to tell which require line is the problem.  Please let me know if there's anything else I can do.

Best,
Ryan

On Thursday, October 25, 2012 5:34:50 PM UTC-7, H. Ryan Jones wrote:

[Anthony Lieuallen]

The best place to make requests is the issue tracker on github, and yes a reproduction case that demonstrates the problem makes things easier to fix.
https://github.com/greasemonkey/greasemonkey/issues