On Tue, Jan 20, 2009 at 08:30:01AM +0100, Alexander Burger wrote:
> > Then a better and generic solution might be that we parse the "Referer:"
> ...
> So I added it to "lib/http.l", available now in the testing release.
Sorry, no. I took it out again.
--
UNSUBSCRIBE: mailto:picol...@software-lab.
Hi Alex,
>> parse the "Referer:"
>
> So I added it to "lib/http.l", available now in the testing release.
thank you, the referer could be useful to have there. I think it
would be good to have all headers the client sent accessible though.
Cheers,
Tomas
--
UNSUBSCRIBE: mailto:picol...@softwar
Hi Alex,
> And it *is* an error if a client tries to access a non-existing
> application.
I would not blame the user for causing an error if she was unfortunate
enough that her session expired and the process handling her session
terminated. The user did not do anything wrong, it can only be the
Hi Tomas,
> Then a better and generic solution might be that we parse the "Referer:"
> ...
> This would be also useful for other purposes, and could be used in the
So I added it to "lib/http.l", available now in the testing release.
Cheers,
- Alex
--
UNSUBSCRIBE: mailto:picol...@software-lab.de
Hi Tomas,
> I think httpGate is
> more complicated than httpGate0 and also it is broken in the sense
> that it does not allow to display a *proper* error or timeout page.
I disagree. 'httpGate' should not try to be clever. It should not
connect to the first port by assuming that somebody will han
Hi Alex,
> But still I want to keep simple things simple. 'httpGate0' connects
> back to the first port without asking, which I think is the worst
> default behavior.
I guess that it depends on the point of view. I think httpGate is
more complicated than httpGate0 and also it is broken in the se
Hi Tomas,
> > ... (though both behaviors are possible with the
> > "void" as well as with your soution), or why it is not powerful
> > enough.
> ...
> example of the default server I sent implements exactly the kind of
> page with timeout you described earlier.
I know. That's what I wrote (should
Hi Alex,
> So with a page pointed to by "void" you can do anything you like,
No, you cannot compute the url where to click/redirect. The url is
hardcoded in the 'void' page.
> I still don't understand why you think it is more user-friendly when
> the user is thrown back to the app's start page
Hi Tomas,
thanks for the proposed solution!
I believe it is useful, but I would not want to put it into the PicoLisp
release.
I still believe the current solution is sufficient, and much simpler. It
does not need additional concepts like a predefined application name, a
session id schema, and a
Hi Alex,
> 1) lib/http.l should have *AppName variable. *AppName could be either
> 2) *SesId should be
> 3) lib/http.l should be changed to allow for "better" handling of
The changed lib/http.l is attached. It should work the same for any
existing deployments as the new behaviour is superset to
Hi Alex,
>> > A direct link to the "default" port might not always be desired, as
>> > this is often not the main application (but some other "home" page).
>>
>> I cannot see how this can be a problem? Having the same
>
> As you know, we are using PicoLisp and 'httpGate' for web applications.
>
Hi Tomas,
> > A direct link to the "default" port might not always be desired, as
> > this is often not the main application (but some other "home" page).
>
> I cannot see how this can be a problem? Having the same
As you know, we are using PicoLisp and 'httpGate' for web applications.
On the d
Hi Alex,
> A direct link to the "default" port might not always be desired, as
> this is often not the main application (but some other "home" page).
I cannot see how this can be a problem? Having the same
configuration, the only difference is that with httpGate you would get
"connection error"
Hi Tomas,
> The above behaviour can be achieved using httpGate0 (attached) and a
> picolisp server bellow running on the default gate of httpGate0:
Thanks for your proposal!
A direct link to the "default" port might not always be desired, as this
is often not the main application (but some other
Hi Tomas,
> Or, do you have some solution for this already?
Sure ;-)
If 'httpGate' fails to connect to the local server, an arbitrary page
can be triggered.
If you look at "src/httpGate.c:262":
if ((srv = gateConnect((unsigned short)port)) < 0) {
logger("Can't connec
Hi Alex,
> when a session expires, user gets connection error. I find that quite
> annoying as the user then have to manually find/enter the starting
> page to log in again. It would be better if the user was "redirected"
> to the starting page again to log in or got a message that his session
>
Hi Alex,
> Here is "home.l":
>
> Now, whenever a HTTP request arrives on port 80 or 443, the 'home'
> function will print a log message, reduce URLs like
> "www.app.7fach.de" to "app.7fach.de", lookup the local URL, and
> redirect the request to that application. Note that from now on the
> applic
Hi Tomas,
> It I use httpGate on port 80, I also lose all logging as done by
> Apache, for example, and cannot use things like webalizer (web log
> statistics tool) any more.
Right, this is quite a disadvantage.
> Isn't httpGate opening potential security hole "tunneling" through to
> any port
Hi Alex,
Thanks for the description of you setup.
>> I have one server only though and do not want to use picolisp
>> server exclusively on that server to serve all my web content.
>
> One possibility would be to either have Apache run on a different
> port, and modify "home.l" in such a way that
Hi Tomas,
> If I understand it well, you have a server with static content
> http://www.software-lab.de/ running apache (and no picolisp
> application) and a server with picolisp web server http://7fach.de/ to
> run picolisp applications (and not any other web server).
Yes.
Running both Apache a
Hi Alex,
> In fact, this is rather the normal case. There is hardly ever a
> server running only a single application.
If I understand it well, you have a server with static content
http://www.software-lab.de/ running apache (and no picolisp
application) and a server with picolisp web server http
Hi Tomas,
> I would like to ask whether you ever deploy multiple picolisp
> applications on a server and if yes what is your setup (assuming the
> only http entrance from outside is the port 80)?
In fact, this is rather the normal case. There is hardly ever a server
running only a single applicat
22 matches
Mail list logo
