When I try to download a .lha file from OS4Depot with AWeb the filename in the ASL requester is always 'download.php'. Is this a problem with OS4Depot or do I need to correct a configuration in AWeb?
When I try to download a .lha file from OS4Depot with AWeb the filename in the ASL requester is always 'download.php'. Is this a problem with OS4Depot or do I need to correct a configuration in AWeb?
There are other sites too where the same happens with Aweb. e.g.: www.c64.com
There are other sites too where the same happens with Aweb. e.g.: www.c64.com
ah-ha! So it's a problem with AWeb. That's too bad since AWeb has the stability IBrowse is currently lacking, but IBrowse has the ability to download correctly. It'll be nice when we get a browser that has both together.
I've talked to one of the aweb guys and they know about the problem, but also said that it's unlikely that they will add this functionality.
There is a way to configure apache to handle this internally somehow (or so I believe anyway), but I have no idea how to configure apache to do that. On some precofigured apache setups it happens, on others not.
A few weeks back when I had to move the site to a backup server (And it's still there) some people reported that the same problem happened in other browsers, seemingly random depending on what ISP they had. But afaik I've fixed that, plus added resume capability during a long programming session digging through http protocol descriptions mixed in with pulling the hair off my head. But I hope that problem is fixed anyway.
I imagine if it was that easy it would have been done by now. Perhaps there is some deeper problem with AWeb.
The main problem is time. The next is wanting to fix it "properly" and not with a hack that will break something else.
As I just hit a suitable point to stop working on the javascript engine, I may take a quick look and see how much work it would take to implement just this feature of Content-Disposition.
It depends alot on where the "decision" about filenames is made within AWeb.
"The "" addressing scheme is not implemented in this version of AWeb" is the message I get in Aweb when I send an URL from Thor.
This is not using OpenURL. I'm using an Arexx script built in with Thor. It used to work fine. But in more recent revisions of AWeb, I can only get this message.
There's another Arexx script in Thor called GetNet which gives two options: either send the URL directly to the browser (gets me the same error message as above) or send it to the hot list of the bowser for later opening. That one works OK with the current AWeb if all I do is send it to the hotlist.
Does that give any clues?
Paul
Builder of Frankenthousand The monster A1000 The Young Frankenthousand A1-XE G4 X5000
I just implemented support for content-disposition so the next AWeb release will work properly.
This may be a good time to remind people that Andy is not only a great programmer but also a musician. Check out his web site and buy a CD or make a donation if you appreciate his efforts on AWeb.
"The "" addressing scheme is not implemented in this version of AWeb" is the message I get in Aweb when I send an URL from Thor.
This is not using OpenURL. I'm using an Arexx script built in with Thor. It used to work fine. But in more recent revisions of AWeb, I can only get this message.
There's another Arexx script in Thor called GetNet which gives two options: either send the URL directly to the browser (gets me the same error message as above) or send it to the hot list of the bowser for later opening. That one works OK with the current AWeb if all I do is send it to the hotlist.
Does that give any clues?
Seems the scripts sends an incomplete url to AWeb, if ever.
If you want you can mail me the AREXX script so i can take a look, wrote myself a script for YAM before it was supported throgh OpenURL, so i know a little something about url handling
IIRC correctly YAM recently changed the way it handles parameters this may be the problem you have. Also I don't know if you are aware of that, but the Rx command (used to interpret Arexx scripts) that came with Upd4 was a bit broken and you had to reinstall the one from Upd3 in order to retreive a fully working Rx command.
Hope that helps...
@Andy
BTW very good job, thank you
I also second the AfxGroup question : when a new version will be released many things were fixed since the latest official release ?