[Glass] Upgrade Grease behind firewall

[Dale Henrichs via Glass]

Bruno,

Since GemStone also calls /usr/bin/curl this is very odd. There _must_ 
be a difference between the full command line used by GemStone and your 
test ... otherwise how can it be explained that curl itself gives two 
different answers?

Dale

On 6/30/16 10:04 AM, BrunoBB via Glass wrote:
> Dale.
>
> Finally i have installed Seaside in GemStone but i have made a very ugly
> thing :)  ;)
>
> It turns out that the problem was in method:
> MetacelloGemStonePlatform>>extractHTTPHeader:do:
>
> Is still under "investigation" why this happend. Inside GS the net packet is
> like:
> HTTP/1.0 200 Connection established
>
> HTTP/1.1 200 OK
> Server: GitHub.com
> .........
>
> But if i do a curl in the command line the answer is like:
> HTTP/1.1 200 OK
> Server: GitHub.com
> ......
>
> So in MetacelloGemStonePlatform>>extractHTTPHeader:do:
> I changed:
> line := aStream nextLine."strip status"
> with:
> line := aStream nextLine; nextLine; nextLine.	"strip status"
>
> And the problem was fixed Seaside is running and working now.
> The person of networking told me that the Reverse Proxy or any other element
> does not change any net packet but he is not 100% sure.
>
> Of course the problem is 100% here. But now has been fixed !
>
> Regards,
> Bruno
>
>
>
>
> --
> View this message in context: http://forum.world.st/Upgrade-Grease-behind-firewall-tp4903625p4904279.html
> Sent from the GLASS mailing list archive at Nabble.com.
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass