[cl-wiki-devel] Problems getting the remote address
I've added a new storage system and the possibility to read and write some meta data together with the page content. But there's one problem left: There's no way to get the remote address of a connected client in the stand-alone version of TBNL. At the moment you can only access this information when you use Apache+mod_lisp+TBNL or a proxy in front of TBNL stand-alone. And I think I have to make a config option to tell CL-WIKI if it's used behind a proxy.
By the way: You need TBNL 0.7.0 or higher for the current version in the darcs repository.
On 2005-09-26 19:52:20, Stefan Scholl wrote:
At the moment you can only access this information when you use Apache+mod_lisp+TBNL or a proxy in front of TBNL stand-alone.
And I think I have to make a config option to tell CL-WIKI if it's used behind a proxy.
The option is called "reverse-proxy" (default NIL) and must be set to t if your stand-alone TBNL is behind a proxy. The saved remote address is NIL when a stand-alone TBNL without reverse proxy is used. Otherwise the address mod_lisp or the header "X-Forwarded-For" (proxy) tells us. I think most of the people will use Apache+mod_lisp or a reverse proxy (e.g. lighttpd+mod_proxy) when the wiki is accessible by the whole wild net. In any other case it's not very important to remember the remote address of every user changing a page.
the whole wild net. In any other case it's not very important to remember the remote address of every user changing a page.
Yes, but why is it so hard to get the IP address of the connected client? That seems ridiculous. Is it not possible to hook the TBNL code to get the IP address? I'll try next week... --vst
On 2005-10-02 13:13:23, Vehbi Sinan Tunalioglu wrote:
the whole wild net. In any other case it's not very important to remember the remote address of every user changing a page.
Yes, but why is it so hard to get the IP address of the connected client? That seems ridiculous. Is it not possible to hook the TBNL code to get the IP address? I'll try next week...
It's a problem with KMRCL, too. Only after changes in KMRCL _and_ TBNL you could access the socket. At the moment just a stream is available. And without the socket no remote address. :-( By the way: Beware of open ports! KMRCL doesn't listen on a specified device. When using mod_lisp or mod_proxy the port is accessible from the outside. But I can't think of any security problems regarding this fact (atm). Regards, Stefan
participants (2)
-
Stefan Scholl -
Vehbi Sinan Tunalioglu