gW3S v2.2.8 released!

[carls]

A new version of the ARexx web server for AmigaOS has been released.
The major new feature of this release is Webalizer-compatible log files (Apache-style). Now you can make pretty graphs and statistics from your gW3S access logs! The problem with Opera on PC (couldn't access gW3S sites) is also fixed and the HTTP support has been enhanced.
gW3S is open source and available for download at http://gonzo.1av10.nu/w3s/

[carls]

This should've been released as "Software" news... My bad. Any of the administrators care to change it? :-)

[mikeymike]

I would, but my parents won't let me use scissors :-)

It would be a bit difficult to have an ARexx script as closed source, wouldn't it... :-)

[carls]

It would be a bit difficult to have an ARexx script as closed source, wouldn't it...

Guess if I've heard that one before ;-P

[Pascal]

It could be possible using JRMS.

[carls]

Hi Pascal :-)

Seriously, I think that scripts can be closed-source, too. Of course, everyone can read the source code but you can have a software license that clearly states that any such changes are forbidden except for private use, or similar. Then it's just up to the user's moral and honesty, as with any other piece of software.

[ikir]

Nice project! Keep up the good work!

[Kent]

I'm curious as to what the problem was with Opera (my preferred browser on the wintel monopoly world) since all gw3s pages loaded fine for me.  What was the header initialization and how did it change from previous version to current?  Was there a line terminator that wasn't being processed properly over the internet in the header components?  As a developer and coauthor of another ARexx web server, I'd love to hear what was done differently.

Also, does GW3S handle cookies yet?  Would be interesting to show some examples on the site.

Keep up the awesome work!  Having not done any work on the ARexx server for a while, it's refreshing to see another person has taken over the reins of a similar beast.

:pint:

[Pascal]

In the "Accept-Encoding:" header it sends, Opera notably states it accepts "x-gzip" and "gzip" encoding. Both mean the same but HTTP specs say "x-gzip" string should be prefered. Therefor, in such a case, former gW3S 2 versions had a priority to answer "Content-Encoding: x-gzip" rather than "Content-Encoding: gzip". In both cases Opera would decodes the file (ex. it requests linked images) but refuses to show the page if "Content-Encoding:" is set to "x-gzip" rather than "gzip"!

gW3S now returns "Content-Encoding: gzip" if it finds "gzip" substring in "Accept-Encoding:" header. This works with all tested browsers.

We're planning on adding cookies handling in gW3S v2.3.