Both instances have been up for 5 days now, looking for more testers.
> On 23 Sep 2021, at 17:03, Sven Van Caekenberghe <[email protected]> wrote: > > Hi, > > Zinc HTTP Components [https://github.com/svenvc/zinc] has been a part of > Pharo since version 1.3 (2011). It is an open-source framework to deal with > the HTTP networking protocol, modelling all aspects involved. It also offers > both client and server functionality. > > The reliability of the code base has improved steadily over the years, thanks > to virtually all Pharo developers using it, directly or indirectly. Over the > summer a number of issues that popped up after Pharo 9 was released were > resolved. > > The robustness of the core HTTP server is one important aspect. To put this > quality further to the test, I deployed two servers with the same demo > Seaside application, Reddit.st, open to the internet, without any further > protections. > > - On Amazon AWS: http://34.245.183.130:1701 > > - On Microsoft Azure: http://51.137.72.94:8080 > > The application's source code can be found at > [https://github.com/svenvc/Reddit]. For the technically curious there are > also deploy instructions at > [https://github.com/svenvc/Reddit/blob/main/DEPLOY.md]. The demo app itself > is described in an older article > [https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740]. > Note that, by definition, there is no HTTPS/TLS variant. > > If you manage to break this server with (a) malicious request(s) in such a > way that you can explain what you did for others to confirm your approach, > you not only help me/us improve the code, but earn eternal fame as well ;-) > > Sven > > PS: I hope I won't regret this, I am looking for constructive criticism. > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org >
