Sounds likely... the #serverXXX settings control the URLs that are
generated by Seaside. If your application is running behind something
like apache that makes the address different than what Seaside would
expect, you should be setting those options.
Julian
On Thu, Oct 16, 2008 at 10:09 PM, Bill Schwab <
[hidden email]> wrote:
> Hello all,
>
> I am working on my reference manager. One of the first things I did
> was create a task for authentication, and that works as intented: give
> it a user name and password it likes, and you are in; it does not allow
> users to register themselves, which is the intended behavior.
>
> Since I switched to https, I now note that timeouts (I think) result in
> an http request which Apache is configured to ignore. I probably just
> need to set the #serverProtocol to 'https', but thought I should ask
> first because I then have to explain why it works the first time
> around.
>
> Any words of wisdom?
>
> Bill
>
>
>
>
>
> Wilhelm K. Schwab, Ph.D.
> University of Florida
> Department of Anesthesiology
> PO Box 100254
> Gainesville, FL 32610-0254
>
> Email:
[hidden email]
> Tel: (352) 273-6785
> FAX: (352) 392-7029
>
> _______________________________________________
> seaside mailing list
>
[hidden email]
>
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
