I have made many bug fixes to improve stability, to both Webber and the HTML Tool, and added some new features to the HTML Tool as well. As a result, Webber now optionally supports the receiving and sending of Cookies.

A simple editor, lets you can view and delete Cookies you may not wish to keep.

Get the update from: https://speccie.uk/software/webber/

On Friday, September 24, 2021 at 3:18:10 AM UTC-5, Speccie wrote:
> I have made many bug fixes to improve stability, to both Webber and the HTML Tool, and added some new features to the HTML Tool as well. As a result, Webber now optionally supports the receiving and sending of Cookies.
>
> A simple editor, lets you can view and delete Cookies you may not wish to keep.
>
> Get the update from: https://speccie.uk/software/webber/
I get webber1.1.x can't be downloaded securely msg when I try to download using chromium browser on my rpi. Is there a way to download not using a https: connection?

On Saturday, September 25, 2021 at 1:10:01 PM UTC-5, Steven Nelson wrote:
> On Friday, September 24, 2021 at 3:18:10 AM UTC-5, Speccie wrote:
> > I have made many bug fixes to improve stability, to both Webber and the HTML Tool, and added some new features to the HTML Tool as well. As a result, Webber now optionally supports the receiving and sending of Cookies.
> >
> > A simple editor, lets you can view and delete Cookies you may not wish to keep.
> >
> > Get the update from: https://speccie.uk/software/webber/
> I get webber1.1.x can't be downloaded securely msg when I try to download using chromium browser on my rpi. Is there a way to download not using a https: connection?

Never mind, I accomplished it. Copied link and pasted into new tab - worked fine.

Steven,

> I get webber1.1.x can't be downloaded securely msg when I try to download using chromium browser on my rpi. Is there a way to download not using a https: connection?

> Never mind, I accomplished it. Copied link and pasted into new tab - worked fine.
As you eventually found, my website can be accessed either with either http:// or https:// from a PC or Mac etc.

On a IIgs itself, you can only access by http://, until someone writes an SSL Link Layer for Marinetti...

Cheers - Ewen (Speccie)

Ewen,

When I launch Webber, I get a message saying that the HTML fonts are
required. As far as I can tell, I have indeed copied all the fonts that are
included in the Fonts folder with Webber, into my System Fonts folder. And I
have all 3 Tools copied into the System Tools folder too.

I'm running System 6.0.1. Any ideas on what might be wrong?

--
]DF$
The New Apple II User's Guide:
https://macgui.com/newa2guide/

David,

> When I launch Webber, I get a message saying that the HTML fonts are required. As far as I can tell, I have indeed copied all the fonts that are included in the Fonts folder with Webber, into my System Fonts folder. And I have all 3 Tools copied into the System Tools folder too. I'm running System 6.0.1. Any ideas on what might be wrong?
Webber wil run in 6.0.1 to 6.0.4.

If you have downloaded and expanded the webber111.bxy package from my website, you will find 27 fonts in the Fonts folder that need to be installed in the System Fonts folder, though you may already have some of them from older installations of Spectrum, SAM2, or Webber.

There are three Tools that need to be installed into the System Tools folder, and they must be the latest ones include with the Webber archive: Tool130, Tool132, and Tool056. You also need the TimeZone CDev installed, and the IIgs clock correctly set for your Time Zone and Daylight Savings setting.

If you have downloaded and used the installer on the webber111.2mg install disk, it will have automatically installed all the required fonts and tools for you.

Once you have rebooted, then all should be well.

The SIS fonts run from SIS.1 to SIS-7, and except for SIS.3, SIS.4, and SIS.5, all have six sizes, from 9-24. There are 27 fonts in all, and they all must be of filetype $C8.

Cheers - Ewen

On 2021-10-02 21:41:53 +0000, D Finnigan said:

> Ewen,
>
> When I launch Webber, I get a message saying that the HTML fonts are
> required. As far as I can tell, I have indeed copied all the fonts that are
> included in the Fonts folder with Webber, into my System Fonts folder. And I
> have all 3 Tools copied into the System Tools folder too.
>
> I'm running System 6.0.1. Any ideas on what might be wrong?

I'm getting this too now. I had everything working perfectly yesterday,
but today...when it gets to the Finder, an error dialog appears:

Error 2: Check that TCP/IP, the HTML Tool, and the SIS fonts, have all
been installed.

They all definitely are. I even reinstalled the Webber components from v1.11.

I can only guess since using Check File to update Check file itself has
this been a problem...or was it Breakdown and Chew Bagger the last
things I installed (before reinstlaling Webber v1.11).

Disabling Check File PIF means the Error 2 dialog doesn't appear on
Finder ready.

However, new error messages now appear for all the apps:

Webber: "Webber Requires HTML Fonts..." you can click OK to return to Finder.

Spectrum: "Requires HTML Tool Error was $8201" (text error that
requires reboot).

Is it possible that older releases of software can overwrite newer
tools, fonts, system extensions?

Just a thought, but I'd like to suggest perhaps only releasing a 32meg,
self booting image that includes any app update in your internet suite
instead of individual releases. That way, you'll know it all works
together with all the dependencies of Marinetti, required fonts, tools,
system extensions, etc. If it can also remove those same tools, fonts,
etc. from the individual installers of each app as part of the suite,
that could remove potential older versions of dependencies as well.

Just an idea, but I imagine most people are using mass storage on a
real IIGS or emulator anyway, so downloading a single source of truth
for the latest version sounds like a potential answer.

Alex

ByteBagger font is problem. Conflict?
2,377 bytes
Created Mon, Oct 22, 2012

David,

> ByteBagger font is problem. Conflict?
That was corrected back in August. Download the latest version of Bytebagger: https://speccie.uk/software/bytebagger/

If you had installed and run Versions, it would have alerted you to that update: https://speccie.uk/software/versions/

Cheers - Ewen

Alex,

> I'm getting this too now. I had everything working perfectly yesterday,
> but today...when it gets to the Finder, an error dialog appears:
> Error 2: Check that TCP/IP, the HTML Tool, and the SIS fonts, have all
> been installed.
> They all definitely are. I even reinstalled the Webber components from v1.11.
> I can only guess since using Check File to update Check file itself has
> this been a problem...or was it Breakdown and Chew Bagger the last
> things I installed (before reinstlaling Webber v1.11).

If you have ByteBagger installed, make sure it is the latest v1.0.7. There was a font conflict with that I fixed: https://speccie.uk/software/bytebagger/

> Disabling Check File PIF means the Error 2 dialog doesn't appear on
> Finder ready.

I will need to check that out, though I assume you are using the latest version 1.0.7 from May this year.

> However, new error messages now appear for all the apps:
> Webber: "Webber Requires HTML Fonts..." you can click OK to return to Finder.
> Spectrum: "Requires HTML Tool Error was $8201" (text error that
> requires reboot).
> Is it possible that older releases of software can overwrite newer
> tools, fonts, system extensions?

That is possible if there are some bugs in the software. ByteBagger can be a culprit though, as it was sharing a font ID with the SIS fonts, so whenever it was in the system, at boot time it would confuse matters. That was fixed back in August.

> Just a thought, but I'd like to suggest perhaps only releasing a 32meg,
> self booting image that includes any app update in your internet suite
> instead of individual releases. That way, you'll know it all works
> together with all the dependencies of Marinetti, required fonts, tools,
> system extensions, etc. If it can also remove those same tools, fonts,
> etc. from the individual installers of each app as part of the suite,
> that could remove potential older versions of dependencies as well.

I do do that with some apps alongside the .BXY version, but it is not practical in most cases, as users would want to copy the app over to their normal running disks, so any problems would remain. Running Versions (without Check File), would show you if any apps of mine were out of date. It also shows you if any of Chris Vavruska’s and Jeremy Rand’s software are out of date as well.

> Just an idea, but I imagine most people are using mass storage on a
> real IIGS or emulator anyway, so downloading a single source of truth
> for the latest version sounds like a potential answer.

I could certainly build a 32 meg disk that held all my software in one place, but they would still have to check that anything there was newer than they had on their working disks, so am not sure if it is a solution. Versions wil find and then download newer versions for you, and you can also use Webber to download newer versions directly to your hard disks.

So far, all the boot error problems with missing fonts etc., have as far as I know been fixed by making sure you are using the latest version of ByteBagger, then that the fonts and tools form the latest archive have been installed.

There are always of course bugs that may lurk in software and that are not found during the Beta testing, These really ought to be reported directly to me using the email address at the end of all my PDF Manuals, as I can react more quickly to them from there.

Cheers - Ewen

Speccie wrote:
>
> If you had installed and run Versions, it would have alerted you to that
> update: https://speccie.uk/software/versions/

Good, from now on I will know to use Versions to check for updates.

Speccie wrote:
>
> On a IIgs itself, you can only access by http://, until someone writes an
> SSL Link Layer for Marinetti...
>

I did some more research on this problem and discovered that an HTTP proxy
server can facilitate access to HTTPS resources. The mod_proxy module in
Apache can also provide access to FTP. It will convert an HTTP GET into an
FTP RETR command.

I already tested this myself and I think it's a viable solution. Take a look
for yourself:

http://httpd.apache.org/docs/2.4/mod/mod_proxy.html

The documentation unfortunately makes the setup appear more complicated than
it actually is. But it's very simple to configure an Apache web server so
that it will accept full HTTPS (or HTTP or FTP) URLs in a GET, and return
the response back over plaintext HTTP.

The proxy server managers the entire TLS scenario, so the client (in this
case, your Webber browser) never sees any of it.

This proxy server could be run on the user's local network, or could be
hosted on any public network. Webber would just need a Preferences option to
allow the user to set the proxy server and port, and then if activated, send
the appropriate requests to this proxy server instead of doing DNS
resolution, etc. to connect directly to that HTTPS or FTP host.

Then, boom! Instant HTTPS support. :-)

--
]DF$
The New Apple II User's Guide:
https://macgui.com/newa2guide/

David,

> I did some more research on this problem and discovered that an HTTP proxy
> server can facilitate access to HTTPS resources. The mod_proxy module in
> Apache can also provide access to FTP. It will convert an HTTP GET into an
> FTP RETR command.

The assumption I made when writing the Proxy software for Webber was that for a Proxy connection, if a HTTPS URL is specified, it should send that out, and if the Proxy server then handles it, all is well. If no Proxy server has been specified, then Webber will change the HTTPS to HTTP and try that.

I tested the Proxy feature using Squid on a Mac, which does link into the Apache server, but it does not pass https URLs, and reports a “not supported” error.

Cheers - Ewen

Hi,

> I did some more research on this problem and discovered that an HTTP proxy
> server can facilitate access to HTTPS resources.

The whole point of networking with the Apple II is to do it without a proxy
server. As soon as you put _ANY_ type of proxy between the Apple II and the
original resource you can as well have a Telnet server running on that
proxy and run appropriate programs (e.g. Lynx) on that proxy.

Just my two cents, Oliver

Speccie wrote:
>
> The assumption I made when writing the Proxy software for Webber was that
> for a Proxy connection, if a HTTPS URL is specified, it should send that
> out, and if the Proxy server then handles it, all is well. If no Proxy
> server has been specified, then Webber will change the HTTPS to HTTP and
> try that.
>
> I tested the Proxy feature using Squid on a Mac, which does link into the
> Apache server, but it does not pass https URLs, and reports a “not
> supported” error.
>

OK, I will give you some more information on my setup. I don't have Squid or
anything else involved. It's just Apache. These are the directives for
Apache. These go in the root server (or virtual host) config file:

ProxyRequests On
ProxyVia Full

-----

Modules that you need to have enabled:

mod_proxy_connect # for HTTPS
mod_proxy_ftp
mod_proxy_http # if you want HTTP proxying

----

With this in place, now your Apache server should accept a request line like
this:

GET https://example.com/example.html HTTP/1.1
Host: webberproxy.speccie.invalid

And it will return the plaintext response from that HTTPS site.

There are also some directives that will cause the proxy to ignore an
expired certificate, or just not validate the certificate. This may or may
not be useful in some cases.

The bigger problem that I don't have a solution for yet, is if you have a
public proxy server, what is the best way to control access to it? To
prevent it from becoming a vehicle for abuse.

--
]DF$
The New Apple II User's Guide:
https://macgui.com/newa2guide/

Oliver Schmidt wrote:
>
> The whole point of networking with the Apple II is to do it without a
> proxy
> server. As soon as you put _ANY_ type of proxy between the Apple II and
> the
> original resource you can as well have a Telnet server running on that
> proxy and run appropriate programs (e.g. Lynx) on that proxy.

I agree, it is unfortunate that there is no TLS library on the Apple II yet.
For people who are interested in achieving the goal of accessing HTTPS web
pages on the Apple II, I think this is the best solution now.

Also the Apache mod_proxy can convert FTP requests into HTTP, which I think
is also useful because you don't have to leave the browser application just
to download a file from an FTP site.

--
]DF$
The New Apple II User's Guide:
https://macgui.com/newa2guide/

Webber Update.

I have just posted an update to Webber, which amongst other bug fixes and some new features, should fix the problems David reported.

You will need to install both the Webber v1.1.2 update, and the included Tool130 v1.5 update.

https://speccie.uk/software/webber/

A week or so ago I released an update to ByteBagger, to fix a crashing problem that I found when opening files.

https://speccie.uk/software/bytebagger/

Cheers - Ewen