Any webpage on ANY Amiga browser?

[DiskDoctor]

Hello,

I recently tried out some 3.x system from AmigaForever pack.
The browser is much outdated but works.

Roughly...

So this is a question rather - is there any proxy server adjusting content to ANY Amiga browser??

If not, it's easy to establish one really.
Two examples:

1) cellphone operators in most cases use proxy for WAP/WAP2 connection - as far as I know its purpose is among others to adjust content to (or check against) xHTML (in WAP2.0)

2) Opera Mini, since released, uses its own proxy server to transform and fit ANY page to ANY cell, even some 128 x . screen(!!)

So, doesn't seem tough.

Maybe I am an ignorant - is there any proxy dedicated to transforming web content for old (ancient) Amiga browsers??

[DiskDoctor]

One more thing - anybody knows how to change UserAgent in AWEB.1 from AmigaForever's AmigaOS3.X??

[DiskDoctor]

Piru wrote:

So, doesn't seem tough.

Famous last words...

I don't get it

[DiskDoctor]

@Piru

It is not tough, at all.

@gurthuk

Google mobile aliases are mess already

Use your e.g. 3.X native browser Try m.google.com or mobile.google.com and switch to mobile device.

What you get... Google sees Amiga UserAgent and considers it unknown (no wonder).  Note that if you were using IE or Firefox or Safari or else, Google would know it and serve you a normal webpage.

But all unknown UAs are considered as very old or odd cellphones.  Old cellphones used WML instead of xHTML so what you get is a WML document, not viewable in any www browser since it's just some XML.

Say, I worked for two years in a mobile industry, enabling new phones in mCMS so that any phone is served properly.  All you gotta do is forge your UserAgent.  It's easy to pick on the web (the string) and if you introduce yourself as a decent WindowsMobile device (e.g. QVGA, VGA maybe), you will be served pure xhtml, formatted to 240 x 320 resolution so fine for Amigas.

So I think it is about to catch HTTP request on a system level and change it, that's all.  I am eager about the result...

[DiskDoctor]

persia wrote:
User Agent is a string provided by your brower.  Most browsers have a plug in to set your user-agent to anything you want, like say Opera-Mini on a Cra or whatever.

Yes, I know it.

My question was about Amiga old browsers - do you know any plugin or rather system script / way of doing this?

I want to play on this OS3.X and see the results.

[DiskDoctor]

That's what I get:

AWeb (www.amigaforever.com)/3.4APL; (Spoofed by Amiga-AWeb/3.4APL)
(it's a string - no link here)


Here is a pretty list.

I would like to change it e.g. to

Mozilla/4.0 (compatible; MSIE 4.01; Windows CE; PPC; 240x320)

There MUST be a script!
I am not able to search this Aminet stuff - always get null answer
But I'll keep trying.

[DiskDoctor]

It is not Amiga, it's AmigaForever software.
But I have 3.X AWeb emulation in it.

It's run on WinXP that has a WiFi connection to my access point which is, in turn, connected to my ISP's cable modem.

I searched Aminet but found and installed only this - it doesn't help.

[DiskDoctor]

bloodline wrote:
@DiskDoctor

It seems a lot of work for the 5 users who insist on using old Amiga Browsers for anything other than novelty value!

I didn't realize it's five users only; my impression was rather that many people do since this very CMS here is supported by old browsers, isn't it?

Also, what about people using 3.X classics?  If I did, I would surely want to use it as FULL desktop system whilst 80% of the desktop feel is a fine web browser nowadays.  This AWeb I'm seeing requires cleanup really.

So this is worth it I think.

[DiskDoctor]

weirdami wrote:
My website works with any browser already.

Good for you.  BTW did you try WAP/WML (1.0, 1.1) enabled cellphone as well?

I meant top sites being visited.  Most (110%) webmasters are testing sites against IE7, IE6, recent FF and eventually Opera.  Safari will be added in two years maybe.

Period.

You will never achieve old Amiga browser support automatically...  Too much of fancy new w3 technologies no one can live without are there.

[DiskDoctor]

The idea behind it is maybe to have such a proxy server that recognizes your browser (by its UA), hence knowing W3 standards it accepts (e.g. HTML version).  Then it forwards http request, introducing itself as an adequate known UA (possibly mobile, too, like WindowsMobile).

My idea is that there are two proxy components
- simple forward using predefined UA list
- forward and (XSL) transformation to the native html code

Since old Amiga browsers are simple, transforming should be pretty simple, too.

How I see it - by clicking "refresh" button, proxy would switch among all possibilities (user agents corresponding to one's browser, plus transformation mode).  Then one could "switch" anytime between content been served, so that he/she picks up most fancy one, probably thoroughly better than original.

See my point?

[DiskDoctor]

I'll try to run my tests as soon as I learn how to spoof my UA under/within AOS3.X.  I have AmigaForever version actually.  Again, anybody knows the way??

As a first run I'll try to collect as much nice "look and feel" UserAgents as possible, mainly mobile, testing on a native browser I have access to.

[DiskDoctor]

Thanks.

But I won't use firefox - I have to look at webpages through my AmigaForever/AWeb so... I have to spoof it at Windows level, I guess.