October 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] ZnClient 403 but 200 in Firefox

by Norbert Hartl

It is done very often. In the past you could solve glitches between browser engines. Nowadays it is done e.g. to discover mobile clients. In one of my services the easiest to keep foreigners out was rejecting all requests which are not zinc ð Norbert > Am 11.10.2018 um 00:32 schrieb HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > > Wow, didn't knew that someone actually could reject/allow specific UAs. > > Thank you Sven, > > Cheers, > > HernÃ¡n > El miÃ©., 10 oct. 2018 a las 17:33, Sven Van Caekenberghe > (<sven(a)stfx.eu>) escribiÃ³: >> >> Because they don't like Pharo or Zinc ;-) >> >> ZnClient new >> systemPolicy; >> beOneShot; >> url: 'http://ifconfig.me/ip'; >> accept: ZnMimeType textPlain; >> headerAt: 'User-Agent' put: 'curl/7.54.0'; >> get. >> >> Changing the User-Agent (effectively lying) works. >> >>> On 10 Oct 2018, at 22:02, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>> >>> When I visit this site http://ifconfig.me/ip using the web browser I >>> get the expected text output. However if I try to do it from Pharo 6.1 >>> (Windows 8.1) I get a 403 forbidden response using this code: >>> >>> ZnClient new >>> systemPolicy; >>> beOneShot; >>> accept: ZnMimeType textPlain; >>> timeout: 6000; >>> url: 'http://ifconfig.me/ip'; >>> get. >>> >>> 2018-09-16 03:06:18 011 Retrying ConnectionTimedOut: Cannot connect to >>> 153.121.72.212:80 >>> 2018-09-16 03:06:19 012 Connection Established ifconfig.me:80 >>> 153.121.72.212 288ms >>> 2018-09-16 03:06:19 013 Request Written a ZnRequest(GET /all.xml) 1ms >>> 2018-09-16 03:06:19 014 Response Read a ZnResponse(403 Forbidden >>> text/html;charset=iso-8859-1 209B) 318ms >>> 2018-09-16 03:06:19 015 GET /all.xml 403 209B 319ms >>> 2018-09-16 03:06:19 016 Connection Closed 153.121.72.212:80 >>> >>> In Firefox this is the output >>> >>> Request Headers Firefox: >>> >>> Host: ifconfig.me >>> User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:62.0) >>> Gecko/20100101 Firefox/62.0 >>> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 >>> Accept-Language: en-US >>> Accept-Encoding: gzip, deflate >>> DNT: 1 >>> Connection: keep-alive >>> Upgrade-Insecure-Requests: 1 >>> >>> Response Headers Firefox: >>> >>> HTTP/1.1 200 OK >>> Date: Sun, 16 Sep 2018 16:47:02 GMT >>> Server: Apache >>> Vary: Accept-Encoding >>> Content-Encoding: gzip >>> Content-Length: 32 >>> Connection: close >>> Content-Type: text/plain >>> >>> >>> Any idea? >>> >>> Cheers, >>> >>> HernÃ¡n >>> >> >> >

Oct. 11, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Norbert Hartl

I really like when I read projects are safed from smalltalkhub. It makes everything so much more manageable > Am 10.10.2018 um 16:59 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > >> On Wed, Oct 10, 2018 at 4:37 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> Sean P. DeNigris wrote >>> I migrated the >>> repo with the hopes that someone in the pharo-contributions organization >>> will copy it. >>> [snip] >>> https://github.com/seandenigris/Artefact >> >> Bump. Anyone? I will do it if you add me to pharo-contributionsâ¦ >> > > Hi Sean, > > Apparently we both moved Artefact to github at the same time. > > This repo contains the project: https://github.com/pharo-contributions/Artefact > > It has: > - Migrated sources > - A new Baseline > - I also moved Stylesheet to github > - I updated the dependency to Units to point to the one of Zweidenker > - Guille fixed the streams problem > > Now we have only one Pharo 7 test failing. I wanted to correct it > before releasing. > >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

Oct. 11, 2018

Re: [Pharo-users] [ANN] Cryptography moved to pharo-contributions

by Norbert Hartl

Well, you can but then the access is not forwarded anymore to the repo youâve transferred. Transferring and forking makes everyone link something they maybe donât want. Transferring and creating a new one with the same name brings all request to the former to your new repo which is unlikely to be wanted. Norbert > Am 11.10.2018 um 07:49 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Why not? > >> On 10 Oct 2018, at 17:55, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> No, that you cannot >> >>> Am 10.10.2018 um 16:36 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: >>> >>> NorbertHartl wrote >>>> The rest is provided by github as long as you do not create a new >>>> repository with the same name. >>> >>> Can you still fork the transferred repo in your personal account? I wasn't >>> sure, which is why I didn't handle Artefact this way. >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >> >> > >

Oct. 11, 2018

Re: [Pharo-users] [ANN] Cryptography moved to pharo-contributions

by Esteban Lorenzano

Why not? > On 10 Oct 2018, at 17:55, Norbert Hartl <norbert(a)hartl.name> wrote: > > No, that you cannot > >> Am 10.10.2018 um 16:36 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: >> >> NorbertHartl wrote >>> The rest is provided by github as long as you do not create a new >>> repository with the same name. >> >> Can you still fork the transferred repo in your personal account? I wasn't >> sure, which is why I didn't handle Artefact this way. >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >

Oct. 11, 2018

Re: [Pharo-users] Why is the root class of tests named TestAsserter?

by Alidra Abdelghani

Hi James, Thanks a lot for this very interesting historical perspective :) Still I think TestAsserter is not the most intuitive name. Asserter is not even an English word if I am not mistaken. Thanks again Abdelghani > On 10 Oct 2018, at 1:57 pm, James Foster <Smalltalk(a)JGFoster.net> wrote: > > Hi Abdelghani, > > I donât have immediate access to earlier versions of SUnit (oh, that it were on GitHub!), but my recollection is that TestCase was originally a root class but duplicate code with TestResource inspired a refactoring that called for a common superclass. The name TestAsserter was chosen to reflect the common behavior. > > James > >> On Oct 9, 2018, at 8:12 AM, Alidra Abdelghani via Pharo-users <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: >> >> >> From: Alidra Abdelghani <alidrandco(a)yahoo.fr <mailto:alidrandco@yahoo.fr>> >> Subject: Why is the root class of tests named TestAsserter? >> Date: October 9, 2018 at 8:12:11 AM PDT >> To: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> >> >> >> Hi, >> >> I am trying to understand how classes in smalltalk projects are named. >> Something I can hardly understand is why the root class of the Test hierarchy is named TestAsserter? >> What is the intention behind the term Asserter? >> Wouldnât it be more appropriate to name it AbstractTest since most classes of this hierarchy are Tests? >> >> Many thanks in advance >> Abdelghani >> >> >> > Dr. Abdelghani Alidra Enseignant-chercheur UniversitÃ© 20 aoÃ»t 1955 SKIKDA-ALGÃRIE Mob:+ 213 550 453 391

Oct. 11, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Sean P. DeNigris

CyrilFerlicot wrote > This repo contains the project: > https://github.com/pharo-contributions/Artefact Great! Mine is now deleted. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 11, 2018

Re: [Pharo-users] Glorp with P3

by Pierce Ng

On Wed, Oct 10, 2018 at 11:12:37AM +0200, Sven Van Caekenberghe wrote: > I know that the actual PSQL DB that I am using has all the Glorp test > tables in it, I forgot whether that happened automatically or not. The Glorp test database is set up by "#GlorpDemoTablePopulatorResource asClass invalidateSetup". In the case of Glorp-SQLite3, that step is done by BaselineOfGlorpSQLite>>postLoadDoIt. Pierce

Oct. 11, 2018

Re: [Pharo-users] ZnClient 403 but 200 in Firefox

by Jerry Kott

A lot of thse types of services do that. Not sure why because itâs so easy to spoof anything in an HTTP(s) request... Jerry Kott This message has been digitally signed. PGP Fingerprint: A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5 > On 10-10-2018, at 3:32 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Wow, didn't knew that someone actually could reject/allow specific UAs. > > Thank you Sven, > > Cheers, > > HernÃ¡n > El miÃ©., 10 oct. 2018 a las 17:33, Sven Van Caekenberghe > (<sven(a)stfx.eu>) escribiÃ³: >> >> Because they don't like Pharo or Zinc ;-) >> >> ZnClient new >> systemPolicy; >> beOneShot; >> url: 'http://ifconfig.me/ip'; >> accept: ZnMimeType textPlain; >> headerAt: 'User-Agent' put: 'curl/7.54.0'; >> get. >> >> Changing the User-Agent (effectively lying) works. >> >>> On 10 Oct 2018, at 22:02, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>> >>> When I visit this site http://ifconfig.me/ip using the web browser I >>> get the expected text output. However if I try to do it from Pharo 6.1 >>> (Windows 8.1) I get a 403 forbidden response using this code: >>> >>> ZnClient new >>> systemPolicy; >>> beOneShot; >>> accept: ZnMimeType textPlain; >>> timeout: 6000; >>> url: 'http://ifconfig.me/ip'; >>> get. >>> >>> 2018-09-16 03:06:18 011 Retrying ConnectionTimedOut: Cannot connect to >>> 153.121.72.212:80 >>> 2018-09-16 03:06:19 012 Connection Established ifconfig.me:80 >>> 153.121.72.212 288ms >>> 2018-09-16 03:06:19 013 Request Written a ZnRequest(GET /all.xml) 1ms >>> 2018-09-16 03:06:19 014 Response Read a ZnResponse(403 Forbidden >>> text/html;charset=iso-8859-1 209B) 318ms >>> 2018-09-16 03:06:19 015 GET /all.xml 403 209B 319ms >>> 2018-09-16 03:06:19 016 Connection Closed 153.121.72.212:80 >>> >>> In Firefox this is the output >>> >>> Request Headers Firefox: >>> >>> Host: ifconfig.me >>> User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:62.0) >>> Gecko/20100101 Firefox/62.0 >>> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 >>> Accept-Language: en-US >>> Accept-Encoding: gzip, deflate >>> DNT: 1 >>> Connection: keep-alive >>> Upgrade-Insecure-Requests: 1 >>> >>> Response Headers Firefox: >>> >>> HTTP/1.1 200 OK >>> Date: Sun, 16 Sep 2018 16:47:02 GMT >>> Server: Apache >>> Vary: Accept-Encoding >>> Content-Encoding: gzip >>> Content-Length: 32 >>> Connection: close >>> Content-Type: text/plain >>> >>> >>> Any idea? >>> >>> Cheers, >>> >>> HernÃ¡n >>> >> >> > >

Oct. 11, 2018

Re: [Pharo-users] ZnClient 403 but 200 in Firefox

by HernÃ¡n Morales Durand

Wow, didn't knew that someone actually could reject/allow specific UAs. Thank you Sven, Cheers, HernÃ¡n El miÃ©., 10 oct. 2018 a las 17:33, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > Because they don't like Pharo or Zinc ;-) > > ZnClient new > systemPolicy; > beOneShot; > url: 'http://ifconfig.me/ip'; > accept: ZnMimeType textPlain; > headerAt: 'User-Agent' put: 'curl/7.54.0'; > get. > > Changing the User-Agent (effectively lying) works. > > > On 10 Oct 2018, at 22:02, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > > When I visit this site http://ifconfig.me/ip using the web browser I > > get the expected text output. However if I try to do it from Pharo 6.1 > > (Windows 8.1) I get a 403 forbidden response using this code: > > > > ZnClient new > > systemPolicy; > > beOneShot; > > accept: ZnMimeType textPlain; > > timeout: 6000; > > url: 'http://ifconfig.me/ip'; > > get. > > > > 2018-09-16 03:06:18 011 Retrying ConnectionTimedOut: Cannot connect to > > 153.121.72.212:80 > > 2018-09-16 03:06:19 012 Connection Established ifconfig.me:80 > > 153.121.72.212 288ms > > 2018-09-16 03:06:19 013 Request Written a ZnRequest(GET /all.xml) 1ms > > 2018-09-16 03:06:19 014 Response Read a ZnResponse(403 Forbidden > > text/html;charset=iso-8859-1 209B) 318ms > > 2018-09-16 03:06:19 015 GET /all.xml 403 209B 319ms > > 2018-09-16 03:06:19 016 Connection Closed 153.121.72.212:80 > > > > In Firefox this is the output > > > > Request Headers Firefox: > > > > Host: ifconfig.me > > User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:62.0) > > Gecko/20100101 Firefox/62.0 > > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > > Accept-Language: en-US > > Accept-Encoding: gzip, deflate > > DNT: 1 > > Connection: keep-alive > > Upgrade-Insecure-Requests: 1 > > > > Response Headers Firefox: > > > > HTTP/1.1 200 OK > > Date: Sun, 16 Sep 2018 16:47:02 GMT > > Server: Apache > > Vary: Accept-Encoding > > Content-Encoding: gzip > > Content-Length: 32 > > Connection: close > > Content-Type: text/plain > > > > > > Any idea? > > > > Cheers, > > > > HernÃ¡n > > > >

Oct. 10, 2018

Re: [Pharo-users] ZnClient 403 but 200 in Firefox

by phil＠highoctane.be

Works for me in a 5.0 Did this c :=ZnClient new systemPolicy; beOneShot; accept: ZnMimeType textPlain; timeout: 6000; url: 'http://ifconfig.me/ip'; yourself. c request headers at: 'User-Agent' put: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0'. c get. Response: 95.182.154.13 Phil On Wed, Oct 10, 2018 at 10:02 PM HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > When I visit this site http://ifconfig.me/ip using the web browser I > get the expected text output. However if I try to do it from Pharo 6.1 > (Windows 8.1) I get a 403 forbidden response using this code: > > ZnClient new > systemPolicy; > beOneShot; > accept: ZnMimeType textPlain; > timeout: 6000; > url: 'http://ifconfig.me/ip'; > get. > > 2018-09-16 03:06:18 011 Retrying ConnectionTimedOut: Cannot connect to > 153.121.72.212:80 > 2018-09-16 03:06:19 012 Connection Established ifconfig.me:80 > 153.121.72.212 288ms > 2018-09-16 03:06:19 013 Request Written a ZnRequest(GET /all.xml) 1ms > 2018-09-16 03:06:19 014 Response Read a ZnResponse(403 Forbidden > text/html;charset=iso-8859-1 209B) 318ms > 2018-09-16 03:06:19 015 GET /all.xml 403 209B 319ms > 2018-09-16 03:06:19 016 Connection Closed 153.121.72.212:80 > > In Firefox this is the output > > Request Headers Firefox: > > Host: ifconfig.me > User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:62.0) > Gecko/20100101 Firefox/62.0 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: en-US > Accept-Encoding: gzip, deflate > DNT: 1 > Connection: keep-alive > Upgrade-Insecure-Requests: 1 > > Response Headers Firefox: > > HTTP/1.1 200 OK > Date: Sun, 16 Sep 2018 16:47:02 GMT > Server: Apache > Vary: Accept-Encoding > Content-Encoding: gzip > Content-Length: 32 > Connection: close > Content-Type: text/plain > > > Any idea? > > Cheers, > > HernÃ¡n > > >

Oct. 10, 2018