-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 error for sessionprotected-counter #1439
Comments
Hi, thanks for reporting. I will keep the issue, in case anyone who uses Squeak with Seaside picks it up and fixes it. This is an issue in the server adaptor for the http server in Squeak only. |
Thanks @jbrichau . I'm new to working Smalltalk and am not too keen on using Pharo at the moment. I'm still just teaching myself Smalltalk so I don't have a huge need for building major web applications at this point and most of Seaside appears to work (e.g. I can go through the tutorials I've found so far without any problems). But yes if you could keep it open maybe I'll get to the point where I can commit a PR to fix :) |
Also I was looking into the open issues and there appears to be a Platform Squeak label - are issues with Squeak generally labeled as such. I'm just trying to get a sense of many issues there are to tackle. I would hate to see Squeak support stop because that list gets too big for anyone to handle in their spare time. I'd love to get proficient enough on this to help out! |
I think this is a duplicate of #1392 WebClient-Seaside-Adaptor-pmm.3.mcz from https://ss3.gemtalksystems.com/ss/WebClient.html should fix it. |
I'm just starting to teach myself Seaside (and still very much learning Smalltalk) and was browsing the example applications just now and noticed the
sessionprotected-counter
example doesn't work and returns a 500 Internal Server error when running in Squeak 6.0 (current release) in the current release of Seaside that was pulled down when I just installed it the other day (v 3.5.9).As I get more comfortable I'll see if I can determine what's causing this.
The text was updated successfully, but these errors were encountered: