tclhttpd-users — Discussion and general Q&A for TclHttpd

[Tclhttpd-users] tclhttpd-configure to set all client website

[Conrad M. <cmo...@gm...>]

Hi,

We are a small ISP,and we would like to setup the following for our
clients.As soon as they open the browser,it must go to our website,but any
new requests will go to the url they entered.Basically we want to 'force'
the clients homepage to be our website.

Someone told me that this can be achieved using tclhttpd,but i do not have a
clue where to start.I know i must install tclhttpd on a server and forward
all port 80 to this server.This is fine,i can do this,but how will i
configure tclhttpd to manage this.If it is a new request from a new
session,go to our website,otherwise go to the intended url.Can tclhttpd do
this,or am i searching at the wrong place?

So just to clarify,client opens his browser,it goes to our website no matter
what his homepage is set to,but any new requests gets passed on to the
intended url from the tclhttpd web server.Any help or pointers will really
be appreciated.

Thanks
Conrad Moolman
South Africa

[Tclhttpd-users] Deleting files fails after broken upload

[Dennis <dan...@ya...>]

Hi,
   
  as mentioned above, i got an error message, on trying to delete an uploaded file, if the upload is canceled manually.
   
  The error message:
   
  Got the error Server Internal Error
while trying to obtain /pool/filedelete. 
error deleting "C:/LS/lsS6XX_srv_v31/Pool/MCAFEE__2007-03-21_10-56.zip": permission denied.
   
  It seems to my, that upload.tcl hangs on waiting eof/new data. Actually the only possibility to delete the incomplete files is to restart tclhttpd.
   
  Is this a clear bug or am I missing something?

  Are there any suggestions for a workaround to solve this problem?
   
  Thanks in forward.
   

 		
---------------------------------
Keine Lust auf Tippen? Rufen Sie Ihre Freunde einfach an.
  Yahoo! Messenger. Jetzt installieren . 

[Tclhttpd-users] tclhttpd on IPv6

[<Gra...@em...>]

Hi,

Can we run the latest tclhttpd package on a pure IPv6 network?=09

regards,
Sukarna

Re: [Tclhttpd-users] Is there a "guide" for how to use sessions?

[Jeff S. <hea...@ya...>]

Hi David,

I think when it comes to sessions and TclHttpd from
what I have read most people tend to 

roll their own even though TclHttpd has a Session
module built in. I think one of the 

reasons they don't use it is because of lack of
Documentation and examples thus your 

question.

I don't know whether the Session module is a good or
bad design but due to my lack of programming
experience I decided it would be a better experience
for me to try and figure out how it worked rather than
reinvent the wheel.

The Documentation summarises how the Session module
works and there is an snmp.tcl file in the TclHttpd
distribution that uses it. I followed this and wrote a
Username and Password database using Metakit. This is
used on a daily basis at my work and has been running
for several years. The Session module is used for
record locking and as well as serialising the write
requests to the database. This works well for Metakit
due to its concurrency limitations.

The Session module has 2 parts. The first part is used
for the Session id stuff and is stored in a state
array. The second part creates a slave interpreter and
excutes the pages in this interpreter. I followed this
approach but after I finished I realised I could have
just used the first part without the second. Refer to
http://wiki.tcl.tk/8657 for an example.

Since I used the Session module it has been enhanced
so there are probably new features available.

Kind Regards

Jeff Smith

--- David Gravereaux <dav...@po...> wrote:

> Hi,
> 
> I need to manage user sessions across different
> pages of a domain script hooked 
> into data I'll have to save/retrieve from a
> database.  I'm not sure where to begin..
> 
> Well, actually, beginning at the login page seems
> most obvious.. But I don't know 
> how to begin the back-end code for it..  Any
> pointers?
> 
> -- 
>     I'm learning real skills that I can apply
> throughout the rest of my life ...
> Procrastinating and rationalizing.  -- Calvin
> 
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
> the chance to share your
> opinions on IT & business topics through brief
> surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> TclHttpd-users mailing list
> Tcl...@li...
>
https://lists.sourceforge.net/lists/listinfo/tclhttpd-users
> 



 
____________________________________________________________________________________
No need to miss a message. Get email on-the-go 
with Yahoo! Mail for Mobile. Get started.
http://mobile.yahoo.com/mail 

[Tclhttpd-users] {Spam?} RE: TclHttpd-users Digest, Vol 7, Issue 2

[yahalome <yah...@xo...>]

We did a basic code to handle sessions. It is basically creates files that
contain the array data. We use xml so the session is sent in the xml. If you
want I can send you the code and you can see what way of doing it.

Yahalom Emet
XPO Team
Xor Financial Solutions
 
Email: yah...@xo...
www.XorTechnologies.com
 
-----Original Message-----
From: tcl...@li...
[mailto:tcl...@li...] On Behalf Of
tcl...@li...
Sent: Thursday, January 25, 2007 1:36 AM
To: tcl...@li...
Subject: TclHttpd-users Digest, Vol 7, Issue 2

Send TclHttpd-users mailing list submissions to
	tcl...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/tclhttpd-users
or, via email, send a message with subject or body 'help' to
	tcl...@li...

You can reach the person managing the list at
	tcl...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of TclHttpd-users digest..."


Today's Topics:

   1. Is there a "guide" for how to use sessions? (David Gravereaux)


----------------------------------------------------------------------

Message: 1
Date: Tue, 23 Jan 2007 22:20:40 -0800
From: David Gravereaux <dav...@po...>
Subject: [Tclhttpd-users] Is there a "guide" for how to use sessions?
To: tcl...@li...
Message-ID: <45B...@po...>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi,

I need to manage user sessions across different pages of a domain script
hooked 
into data I'll have to save/retrieve from a database.  I'm not sure where to
begin..

Well, actually, beginning at the login page seems most obvious.. But I don't
know 
how to begin the back-end code for it..  Any pointers?

-- 
    I'm learning real skills that I can apply throughout the rest of my life
...
Procrastinating and rationalizing.  -- Calvin



------------------------------

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

------------------------------

_______________________________________________
TclHttpd-users mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tclhttpd-users


End of TclHttpd-users Digest, Vol 7, Issue 2
********************************************

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

__________ NOD32 2001 (20070124) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[Tclhttpd-users] Is there a "guide" for how to use sessions?

[David G. <dav...@po...>]

Hi,

I need to manage user sessions across different pages of a domain script hooked 
into data I'll have to save/retrieve from a database.  I'm not sure where to begin..

Well, actually, beginning at the login page seems most obvious.. But I don't know 
how to begin the back-end code for it..  Any pointers?

-- 
    I'm learning real skills that I can apply throughout the rest of my life ...
Procrastinating and rationalizing.  -- Calvin

[Tclhttpd-users] Usage of the Config array

[Kristoffer L. <se...@fi...>]

I am finding some rather weird behaviour in the use of the tclhttpd  
Config variable. config.tcl loads the whole config file into a  
variable in its own namespace. In the main file cmdline::getoptions  
reads a certain set of vars into a global Config variable, but not all.

Now, the problem is that at least the auth.tcl file checks for  
options by directly looking at the global Config variable. Things  
such as the following:

if {![info exists Config(AuthUserFile)]} {
     set Config(AuthUserFile) default
}

In this situation Config(AuthUserFile) will never be set. Is this a  
clear bug or am I missing something?

            /  http://www.fishpool.com/~setok/

Re: [Tclhttpd-users] virtual hosts

[Steve B. <st...@pr...>]

Thank you both for your swift and lucid responses.   My situation is that I
use tclhttpd to provide encrypted scripts to run on a (software)
thin client.   Different instances of the server supply tailored
scripts, and talk to different MetaKit databases, for different user
populations.   Lots of custom code, extracted from databases on the
server, put together on an individual basis for different users.   But
overall, the data rate is low.   At present I do it by aliasing IP
addresses onto the same physical server, but if there were a way of
handling it without using up so much address space I would try to use
it.   So this is not a standard web server use at all, more a supplier
of special applications.

Kind regards,

--
Steve Blinkhorn <st...@pr...>

>>>Jan Kandziora said:
 > Am Dienstag, 7. November 2006 16:14 schrieb Steve Blinkhorn:
 > >
 > > What about multiple software servers, i.e. instances of tclhttpd, each
 > > responding to a different virtual domain but using the same port
 > > number, although on just one IP address?   And when did this feature
 > > arrive in tclhttpd? (I am a long-term user, BTW).
 > >
 > Two or more processes cannot listen (to all) on the same port number on the 
 > same machine. It's just the way TCP/IP works.
 > 
 > To achieve something like you may think of, you have to build a "proxy" 
 > listener, which dispatches the accepted connections to slave processes. 
 > Hence, this usually (virtual domains, not just parallizing or load-balancing
     ) 
 > involves the investigation of the "Host:" HTTP header field, which is the 
 > only way to check which server should get the connection.
 > 
 > So your question sounds pretty pointless to me.
 > 

Re: [Tclhttpd-users] virtual hosts

[Reinhard M. <ma...@tc...>]

Hi,

On Tue, 7 Nov 2006 at 16:25, Jan Kandziora wrote:

> Two or more processes cannot listen (to all) on the same port number 
> on the same machine. It's just the way TCP/IP works.

not entirely true. It is possible to have multiple listeners on the 
same port on the same machine, if the machine has multiple IP 
addresses and each listener binds to a different one.

cu
	Reinhard

Re: [Tclhttpd-users] virtual hosts

[Reinhard M. <ma...@tc...>]

Hi,

On Tue, 7 Nov 2006 at 15:14, Steve Blinkhorn wrote:

> What about multiple software servers, i.e. instances of tclhttpd, 
> each responding to a different virtual domain but using the same 
> port number, although on just one IP address?

That wouldn't work. TCP/IP doesn't know about host names and so 
doesn't have a way to distinguish between connections to the domains A 
and B if both servers listen on the same IP address and port name.

Or did you mean the machine has multiple IP addresses and each server 
listens on a different one? That would work, but be a waste of IP 
addresses and is the very reason why the possibility to run web 
service for multiple domains through a single IP/port pair was added 
to the HTTP protocol.

Also, multiple tclhttpd processes running on a single machine might 
consume more resources (especially memory) than using a single 
instance. OTOH, there might be valid reasons for running separate 
instances, e.g. for privilege separation or fail safety.

> And when did this feature arrive in tclhttpd?

IIRC it was one or two releases ago.

cu
	Reinhard

Re: [Tclhttpd-users] virtual hosts

[Jan K. <jj...@gm...>]

Am Dienstag, 7. November 2006 16:14 schrieb Steve Blinkhorn:
>
> What about multiple software servers, i.e. instances of tclhttpd, each
> responding to a different virtual domain but using the same port
> number, although on just one IP address?   And when did this feature
> arrive in tclhttpd? (I am a long-term user, BTW).
>
Two or more processes cannot listen (to all) on the same port number on the 
same machine. It's just the way TCP/IP works.

To achieve something like you may think of, you have to build a "proxy" 
listener, which dispatches the accepted connections to slave processes. 
Hence, this usually (virtual domains, not just parallizing or load-balancing) 
involves the investigation of the "Host:" HTTP header field, which is the 
only way to check which server should get the connection.

So your question sounds pretty pointless to me.

Kind regards

	Jan
-- 
Jetzt neu: "Microsoft Direct-Visual-Active-Office-Plusplus-Pro Service Pack"

Re: [Tclhttpd-users] virtual hosts

[Steve B. <st...@pr...>]

>>>Reinhard Max said:
 > Hi,
 > 
 > On Tue, 7 Nov 2006 at 14:33, Steve Blinkhorn wrote:
 > 
 > > For example, what does a virtual host name look like?
 > 
 > it looks like any other hostname. Virtual servers (in the http world) 
 > means that multple DNS records point to the same IP address and the 
 > server there is supposed to deliver different content depending on the 
 > name that was used. For that, the client adds a "Hostname:" field to 
 > the HTTP request to tell the server which of the virtual domains it is 
 > querying.
 > 
 > > In what sense is this feature an improvement over multiple servers 
 > > each on a separate connection?
 > 
 > You can save a lot on hardware, power and IP address space by placing 
 > many low-volume sites as virtual domains on a single physical machine 
 > with a single IP address.
 > 

What about multiple software servers, i.e. instances of tclhttpd, each
responding to a different virtual domain but using the same port
number, although on just one IP address?   And when did this feature
arrive in tclhttpd? (I am a long-term user, BTW).

--
Steve Blinkhorn <st...@pr...>

Re: [Tclhttpd-users] virtual hosts

[Reinhard M. <ma...@tc...>]

Hi,

On Tue, 7 Nov 2006 at 14:33, Steve Blinkhorn wrote:

> For example, what does a virtual host name look like?

it looks like any other hostname. Virtual servers (in the http world) 
means that multple DNS records point to the same IP address and the 
server there is supposed to deliver different content depending on the 
name that was used. For that, the client adds a "Hostname:" field to 
the HTTP request to tell the server which of the virtual domains it is 
querying.

> In what sense is this feature an improvement over multiple servers 
> each on a separate connection?

You can save a lot on hardware, power and IP address space by placing 
many low-volume sites as virtual domains on a single physical machine 
with a single IP address.

cu
	Reinhard

[Tclhttpd-users] virtual hosts

[Steve B. <st...@pr...>]

Is there something a little fuller than the wiki page on this?   For
example, what does a virtual host name look like?   In what sense is
this feature an improvement over multiple servers each on a separate
connection?

--
Steve Blinkhorn <st...@pr...>

Re: [Tclhttpd-users] Advice on embedding Tclhttpd

[Michael S. <sc...@un...>]

Trevor Davel schrieb:
> Hi everyone,
>  
> I have recently started to look at Tclhttpd as a means to provide a web
> interface to an application.  My team has used Tcl to develop products
> before
> and we have a function library we'd like to use in a new application, but
> a web interface may be more appropriate than the Tk interfaces we have
> previously developed.
>  
> Tclhttpd looks like it can do the job, but I have some concerns and I'd
> like
> to know if anyone can give me some advice.
>  
> Reliability & Security
>  
> There are a couple of comments and testimonials around concerning the
> stability
> and reliability of Tclhttpd, and they seem to be positive.  On the other
> hand
> I have seen little comment on the security of Tclhttpd. 
>  
> I am also concerned by the apparent lack of development -- this could
> indicate
> a lack of use & support, or product maturity ;)
>  
> Can anyone comment on Tclhttpd's reliability and security, preferably with
> reference to case studies in a hostile production environment?
>  
> What about the pace of development?  For example, bug [1446208] (server
> is open
> for xss attacks) was opened in March 2006 -- I would have thought XSS
> bugs would
> deserve high priority?  Is there a roadmap for 3.5.x / 3.6, given that
> 3.5.1 is
> over two years old?
There is not much development on Tclhttpd. If you want a newer
alternative, take a look at WUB:
 http://wiki.tcl.tk/wub

Other options:
http://wiki.tcl.tk/15244

Regarding the XSS attack you mentioned. As far as i can remember those
only happen inside the password protected admin area or with debug
settings on, so they are no real problem unless the admin is utterly stupid.

Other comments on security: Tclhttpd is ok, although it is easy to DOS
the machine, as it uses gets for its network interaction.
See http://www.tcl.tk/cgi-bin/tct/tip/287.html for some background of
the problem there.

One easy way to isolate tclhttpd from the rest of the application is
listed in:
http://wiki.tcl.tk/8755

Would need some work (aka security policies written) to run inside
something like the Safe_Base) as a restricted and very secure web server.

Michael

Re: [Tclhttpd-users] Advice on embedding Tclhttpd

[Jan K. <jj...@gm...>]

Am Montag, 6. November 2006 14:42 schrieb Jan Kandziora:
> > What I think I am aiming for is to have a reusable, embeddable httpd
> > package.
> > Something like this:
> >   % package require embedhttpd
> >   1.0
> >   % embedhttpd::init -host 127.0.0.1 -port 81 -webmaster
> > <mailto:xx...@yy...> xx...@yy...
> >
> >   % embedhttpd::error_handler my_error_proc
> >   my_error_proc
> >   % embedhttpd::url_handler / my_root_proc
> >   / my_root_proc
> >   % embedhttpd::start
> >   Server listening on 127.0.0.1:81
> >
> > So my question is: has anyone done something like this before, and do you
> > have
> > some advice for me? ;)
>
An addition: The first thing to achieve would be getting rid of all "global" 
commands in the tclhttpd source in favor of "variable" commands. After this 
is done, the tclhttpd sources could be "source"d in the embedhttpd namespace.

Kind regards

	Jan
-- 
A truly stable environment would be a concrete basement with no
windows! Computers are no different.

Re: [Tclhttpd-users] Advice on embedding Tclhttpd

[Jan K. <jj...@gm...>]

Am Montag, 6. November 2006 10:42 schrieb Trevor Davel:
>
> I am also concerned by the apparent lack of development -- this could
> indicate a lack of use & support, or product maturity ;)
>
I am using tclhttpd as an "configuration webserver" in a commercial product.

So far, I had no big problems with it. Most annoying for me was tclhttpd comes 
as a script to be sourced, not as a proper tcl package. So it can be a little 
tricky to put it into another tcl application.

On the other hand, the code is more or less easy to understand and patches are 
easy to develop, as soon you had diven into it.


Lack of development -- I would say, tclhttpd is kind of abadoned. I myself had 
put a (not proper, though) patch on this list, which allows "Content 
encoding: gzip;". Not a single reply... 

If Jeffrey or Brent aren't interested in tclhttpd any more, I presume someone 
(we) should adopt this project. I have great interest in tclhttpd as it is 
neccessary for my application.


> Can anyone comment on Tclhttpd's reliability and security, preferably with
> reference to case studies in a hostile production environment?
>
> What about the pace of development?  For example, bug [1446208] (server is
> open
> for xss attacks) was opened in March 2006 -- I would have thought XSS bugs
> would
> deserve high priority?  Is there a roadmap for 3.5.x / 3.6, given that
> 3.5.1 is
> over two years old?
>
Well, Cross-Site-Scripting vulnerability is heavily dependent on the content 
generated. The web server itself doesn't do much processing of the input 
data, so I'm pretty sure it could be cured very easily if there happens to be 
a hole (in the web server, not just in the example pages).


> Embedding Tclhttpd
>
> The application we are developing is not simply a web app -- it is a
> service with various interfaces that performs periodic processing.  In
> short we want to use Tclhttpd to provide an interface, not to provide the
> structure of the application.  In addition, the web interface will be
> entirely dynamic -- we have
> no need to serve files.
>
Ah! Same here.


> And this is where my real problems start ;)
>
> With some effort I have reworked the httpd.tcl and httpdthread.tcl startup
> files
> to remove all file system access, and pared down the required library files
> until I found a minimal set that (sort-of) works.  I have done this in an
> attempt to ensure that certain functionality is strictly unavailable.
>
> I am still facing a bunch of bugs because the internals of Tclhttpd assume
> the
> availability of various commands, and some of those commands are not
> obvious (i.e. they are only called from error paths).  For example,
> Doc_Error is called by Url_Unwind (which handles exceptions in the
> dispatcher), but doesn't
> work properly without the httpd::doc package, which provides filesystem
> access
> and pulls in most of the functionality of Tclhttpd ;(
>
Is it absolutely neccessary in your application to have *no* file system 
access? For my application, I just tuned the document root to an empty 
directory and worked with "Direct_Url" only.


>
> What I think I am aiming for is to have a reusable, embeddable httpd
> package.
> Something like this:
>   % package require embedhttpd
>   1.0
>   % embedhttpd::init -host 127.0.0.1 -port 81 -webmaster
> <mailto:xx...@yy...> xx...@yy...
>
>   % embedhttpd::error_handler my_error_proc
>   my_error_proc
>   % embedhttpd::url_handler / my_root_proc
>   / my_root_proc
>   % embedhttpd::start
>   Server listening on 127.0.0.1:81
>
> So my question is: has anyone done something like this before, and do you
> have
> some advice for me? ;)
>
My goal, too. Unfortunately, I found no time working on that so far. Your code 
below reads good...

Kind regards

	Jan
-- 
Alles Schwere kommt von oben...

[Tclhttpd-users] Advice on embedding Tclhttpd

[Trevor D. <Tr...@pr...>]

Hi everyone,
 
I have recently started to look at Tclhttpd as a means to provide a web 
interface to an application.  My team has used Tcl to develop products
before
and we have a function library we'd like to use in a new application, but 
a web interface may be more appropriate than the Tk interfaces we have
previously developed.
 
Tclhttpd looks like it can do the job, but I have some concerns and I'd like

to know if anyone can give me some advice.
 
Reliability & Security
 
There are a couple of comments and testimonials around concerning the
stability
and reliability of Tclhttpd, and they seem to be positive.  On the other
hand
I have seen little comment on the security of Tclhttpd.  
 
I am also concerned by the apparent lack of development -- this could
indicate
a lack of use & support, or product maturity ;)
 
Can anyone comment on Tclhttpd's reliability and security, preferably with
reference to case studies in a hostile production environment?
 
What about the pace of development?  For example, bug [1446208] (server is
open
for xss attacks) was opened in March 2006 -- I would have thought XSS bugs
would
deserve high priority?  Is there a roadmap for 3.5.x / 3.6, given that 3.5.1
is
over two years old?
 
Embedding Tclhttpd
 
The application we are developing is not simply a web app -- it is a service
with various interfaces that performs periodic processing.  In short we want
to use Tclhttpd to provide an interface, not to provide the structure of the
application.  In addition, the web interface will be entirely dynamic -- we
have
no need to serve files.
 
And this is where my real problems start ;)
 
With some effort I have reworked the httpd.tcl and httpdthread.tcl startup
files
to remove all file system access, and pared down the required library files 
until I found a minimal set that (sort-of) works.  I have done this in an 
attempt to ensure that certain functionality is strictly unavailable.
 
I am still facing a bunch of bugs because the internals of Tclhttpd assume
the
availability of various commands, and some of those commands are not obvious
(i.e. they are only called from error paths).  For example, Doc_Error is 
called by Url_Unwind (which handles exceptions in the dispatcher), but
doesn't
work properly without the httpd::doc package, which provides filesystem
access
and pulls in most of the functionality of Tclhttpd ;(
 
I have looked at minihttpd and it doesn't seem to be an appropriate solution
--
I'm looking for a solution that is a little more functional (and tested).
I am also aware of http://wiki.tcl.tk/10198 <http://wiki.tcl.tk/10198>
(minimal tclhttpd) but it seems to
be a couple of years out of date ;(
 
What I think I am aiming for is to have a reusable, embeddable httpd
package.
Something like this:
  % package require embedhttpd
  1.0
  % embedhttpd::init -host 127.0.0.1 -port 81 -webmaster
<mailto:xx...@yy...> xx...@yy...
  
  % embedhttpd::error_handler my_error_proc
  my_error_proc
  % embedhttpd::url_handler / my_root_proc
  / my_root_proc
  % embedhttpd::start
  Server listening on 127.0.0.1:81
  
So my question is: has anyone done something like this before, and do you
have
some advice for me? ;)
 

Thanks,
Trevor (Twylite)
 

# Minimal embeddable Tclhttpd
 
# Only the following lib files are required:
# cookie.tcl
# direct.tcl
# httpd.tcl
# log.tcl
# logstd.tcl
# pkgIndex.tcl
# url.tcl
# utils.tcl
# version.tcl
 
package require md5   ;# required by httpd::utils but not used in this httpd
package require ncgi  ;# needed to parse http requests
package require httpd ;# main server
package require httpd::version ;# version information
package require httpd::log     ;# server has Log calls in various places
package require httpd::utils   ;# one or two functions used in other places
package require httpd::url     ;# URL dispatcher, part of main server
package require httpd::cookie  ;# easy access to cookies, required by direct
package require httpd::direct  ;# direct URL domain support
 

# Required for non-threaded implementation
proc Thread_Respond {args} {return 0}
proc Thread_Enabled {} {return 0}
 
set use_httpd_counter 0
if { $use_httpd_counter } {
  package require httpd::counter
} else {
  # I don't really care about counting & statistics, but httpd expects
  # these functions to be available
  proc Counter_Init {args} { }
  proc Count {what {delta 1}} { }
  proc CountName {instance tag} { }
  proc CountHist {what {delta 1}} { }
  proc CountStart {what instance} { }
  proc CountStop {what instance} { }
}
 
# httpd::direct uses Cgi_SetEnv to provide an environment to direct URL
# procs -- I don't really care about that
proc Cgi_SetEnv {sock path {var env}} { }
 

# If you don't have doc_error.tcl you'll need to define Doc_NotFound and 
# Doc_Error
 
proc Doc_NotFound { sock } {
  Httpd_ReturnData $sock text/html "Not found"
 Httpd_Error $sock 404 
}
 
proc Doc_Error { sock ei } {
  Httpd_ReturnData $sock text/html "Internal error"
 Httpd_Error $sock 500 
}
 

# Set up the dynmaic domain handler for the root URL
 
Direct_Url / rooturl
proc rooturl {} { return <html><body>Alpha</body></html> }
 
# The URL dispatcher has a problem with / is the only domain and it is set
# up using direct.  Workaround is to create an additional direct URL prefix.
 
Direct_Url /dummy rooturl
 
# Initialise the server
 
Httpd_Init
Counter_Init 60
Httpd_Webmaster xx...@yy... <mailto:xx...@yy...> 
Httpd_Server 81 localhost 127.0.0.1
 

NOTICE :  this electronic mail and any attachments ("message") contains
privileged information intended only for the addressee(s) use.  If you are
not the/an intended recipient, you may not disclose, review, disseminate,
retransmit, copy, use or take action in reliance upon or otherwise deal with
or publish this message, which is subject to copyright ("Use").  You may not
use this message for anything other than the purpose for which it is
intended.  If you have received this message in error, you are required to
notify the writer and delete it. Prism Holdings Limited, its holding
companies and its subsidiaries ("Prism") accept no liability whatsoever as a
result of any losses arising from persons placing reliance on any
information contained in this message or and Use thereof.  The views
expressed in this message are those of the individual transmitting it,
unless they are expressly stated to be those of Prism.  It is the
recipient's obligation to scan this message and ensure that it contains no
viruses or other malicious programs and the recipient is warned that,
notwithstanding reasonable checks performed by Prism, viruses and harmful
programs may be contained in this message and Prism accepts no liability
whatsoever for any loss, damage, or liability of any nature, whether direct
or indirect, resulting from the recipient accessing or Using this message or
any files attached to it.

[Tclhttpd-users] problem in Httpd_ReturnFile?

[David G. <dav...@po...>]

I'm getting these entries in my error log file:

 [04/Oct/2006:14:57:13] iocp772 error writing "iocp772": connection
reset by peer  /baby/birth/firstbath1.png
 [04/Oct/2006:14:57:17] iocp868 error writing "iocp868": connection
reset by peer  /baby/birth/grandma.png
 [04/Oct/2006:14:58:13] iocp772 read error during state start: error
reading "iocp772": connection reset by peer
 [04/Oct/2006:14:58:18] iocp868 read error during state start: error
reading "iocp868": connection reset by peer


The first 2 are good, but the last 2 are not.  I know this is 95% my
fault as I'm running some alpha code with IOCPSOCK doing the tcp channel
driver, but I'm having a bit of a difficult time reading the tclhttpd
script files.  I know I should cheat and run all this in a tcl debugger
and trace through script execution that way to come to an understanding
of it all, but maybe I'm a bit lazy..

Anyways..

I see in Httpd_ReturnFile it calls Httpd_Suspend which turns off the
file events and lets fcopy proceed with a background transfer.  If the
fcopy fails with a transfer error (like ECONNRESET above) see
HttpdCopyDone, shouldn't the socket be closed permanently and not just a
1.1 reset?  It looks to me like the socket is just being reset and
restarted to HttpdRead instead of dumped.

/me off to trace this deeper..

most likely this is my fault with my channel driver, but can't seem to
isolate where I'm getting tclhttpd confused.

-- 
David Gravereaux <dav...@po...>
$ make war
make: *** No rule to make target `war'.  Stop.  Try `love' instead

[Tclhttpd-users] HTTP with Content-Encoding: gzip

[Jan K. <jj...@gm...>]

Dear all,

I use TclHttpd for the web driven configuration of an embedded device. For 
some reason, I have to generate rather big (1MB) HTML pages for some 
configuration screens. When doing remote support, one would have to upload 
this much information through a 128kBit/s or modem line, which would be very 
disturbing to work with.

HTTP has an optional return-header "Content-Encoding", which allows to e.g. 
gzip the data on the server side and the browser will automagically gunzip 
it. As tclhttpd doesn't support this useful feature, I'd written some lines 
myself. The Trf package (http://sourceforge.net/projects/tcltrf) and good ol' 
zlib are used to do the actual compression. 

It's not beautified nor in proper patch format right now  -- I just wonder if 
anyone of you is interested in this, too. Please see the attachment.

Kind regards

	Jan
-- 
Really, I'm not out to destroy Microsoft. That will just be a
completely unintentional side effect. -- Linus Torvalds

Re: [Tclhttpd-users] [Fwd: Access Control in tclhttpd]

[Daniel S. <dan...@ya...>]

Was there any follow-up to this one? 
 
I am having the exact same problem.  I search c.l.t also and did not  find anything. 
 
I am running Windows XP SP2 and tclhttpd3.5.1.kit.  I have also created  a c:\tmp directory to solve the startup issue. 
 
I have Activetcl8.4.11.0 installed and I start by double clicking the  icon of tclhttpd3.5.1 
 
But like Sven I cannot get to browse to /htaccess. 
 
I am trying to log with username:  webmaster and the password found in  tmp\tclhttpd.default 
 
I have also try the CVS nigthly version with no results. 
 
Thanks in advance. 
 
From: Colin McCormack <colin@ch...> 
Re: [Fwd: Access Control in tclhttpd]   2004-09-30 23:47 
 
Thanks Erik, 
 
I"ll take this offline and see if Svenn and I can work out what"s going 
on.  If there"s general value, I"ll feed it back. 
 
Colin. 
 
On Fri, 2004-10-01 at 04:21, Erik Leunissen wrote: 
> Forwarded from c.l.t. 
>  > -------- Original Message -------- 
> Subject: Access Control in tclhttpd 
> Date: 27 Sep 2004 13:20:57 -0700 
> From: svenn.are@bj... 
> Organization: http://groups.google.com 
> Newsgroups: comp.lang.tcl 
>  > Hi, 
>  > I have installed vanilla tclhttpd 3.5.1 on my winxp machine to have a 
> httpd server to run usemod wiki as a cgi-bin. I cannot use apache as 
> its install wants to access the registry which is closed for userland 
> modifications. Tclhttpd runs fine and I can browse the pages contained 
> in the default distribution. 
>  > Except the password protected pages. 
>  > I have read the acces control page and see that in order to create 
> users and passwords I should use the Access Control Editor with the 
> usernale webmaster and the password that is saved in 
> c:\tmp\tclhttpd.default. I notice that tclhttpd recreates a new 
> password each time I start the server, but when I want to access the 
> Access Control Editor with the username and the currently generated 
> password, I get no access. 
>  > I have looked around on tcl"ers wiki and in the Practical Programming 
> in Tcl and Tk and searched the group without getting any wiser. 
> The Use of Access Editor talks about AuthUserFile and AuthGroupFile, 
> but they are supposed to live in /usr/local/htaccess which I guess is 
> unix only. 
>  > I found a passwd and a group file in 
> c:\tcl\lib\tclhttpd3.5.1\htaccess\win32 but I don"t know what to do 
> with them as I guess they contain encrypted passwords. 
>  > Does anybody have a stupid end users guide to getting access control 
> right on tclhttpd? 
-- 
Colin McCormack <colin@ch...>
 		
---------------------------------
Lèche-vitrine ou lèche-écran ? Yahoo! Magasinage.

Re: [Tclhttpd-users] TclHttpd-users Digest, Vol 3, Issue 3

[Scott G. <sg...@ya...>]

On my router, I configured it to forward port 80 to the IP address that has my web server.  So, for example, you would configure your router to forward requests to port 80 to 192.168.0.3.  

----- Original Message ----
From: tcl...@li...
To: tcl...@li...
Sent: Monday, August 21, 2006 12:03:22 PM
Subject: TclHttpd-users Digest, Vol 3, Issue 3

Send TclHttpd-users mailing list submissions to
    tcl...@li...

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.sourceforge.net/lists/listinfo/tclhttpd-users
or, via email, send a message with subject or body 'help' to
    tcl...@li...

You can reach the person managing the list at
    tcl...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of TclHttpd-users digest..."


Today's Topics:

   1. new to Tclhttpd (suchod)


----------------------------------------------------------------------

Message: 1
Date: Mon, 21 Aug 2006 20:59:14 +0200
From: suchod <su...@wa...>
Subject: [Tclhttpd-users] new to Tclhttpd
To: tcl...@li...
Message-ID: <44E...@wa...>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello
my pc is under windows xp family service pack 2
Tcl/Tk 8.4.11 and Tclhttpd3.5.1 as a starkit
I have a netgear router adsl and 3 pc in three ethernet slots
my IP address is dynamic
**
In my router I have given my machine a fixed lanAddress
192.168.0.3 and then enabled the HTTP server service and
activated the DMZ capability on this address
**
when i start Tclhttpd "as is" it works very well on "localhost:8015"
**
Then i start it on command line with "-port 80" and it work very well
on "localhost"
***
My browser is "firefox 1.5.0.4" and when i give it my "ip address"
for instance "http://81.249.174.44"; or "http://81.249.174.44:8015";
i cannot get the start page.
****
i have been through book documentation,  comp.lang.tcl archives,
google,  etc... and have no valid idea.
thank you in advance if you can help me
friendly
jerome




------------------------------

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

------------------------------

_______________________________________________
TclHttpd-users mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tclhttpd-users


End of TclHttpd-users Digest, Vol 3, Issue 3
********************************************

[Tclhttpd-users] new to Tclhttpd

[suchod <su...@wa...>]

Hello
my pc is under windows xp family service pack 2
Tcl/Tk 8.4.11 and Tclhttpd3.5.1 as a starkit
I have a netgear router adsl and 3 pc in three ethernet slots
my IP address is dynamic
**
In my router I have given my machine a fixed lanAddress
192.168.0.3 and then enabled the HTTP server service and
activated the DMZ capability on this address
**
when i start Tclhttpd "as is" it works very well on "localhost:8015"
**
Then i start it on command line with "-port 80" and it work very well
on "localhost"
***
My browser is "firefox 1.5.0.4" and when i give it my "ip address"
for instance "http://81.249.174.44" or "http://81.249.174.44:8015"
i cannot get the start page.
****
i have been through book documentation,  comp.lang.tcl archives,
google,  etc... and have no valid idea.
thank you in advance if you can help me
friendly
jerome

Re: [Tclhttpd-users] Linux Startup with port 80

[Nikos <ni...@ma...>]

Paul Nash wrote:

> What is the best way to have tclhttpd automatically startup under 
> Linux (Suse 9.3). The server is currently in a user home directory 
> -uid 1000 -gid 100.
>  
> Regards, Paul Nash
>
>------------------------------------------------------------------------
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys -- and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
>------------------------------------------------------------------------
>
>_______________________________________________
>TclHttpd-users mailing list
>Tcl...@li...
>https://lists.sourceforge.net/lists/listinfo/tclhttpd-users
>  
>
Hi,

This sample init comes with the distro...

edit accordingly...

#!/sbin/sh
#
# /etc/init.d/tclhttpd - Start/Stop the tcl httpd server
#
# This file lives in slightly different locations on different platforms:
# Solaris:
# IRIX:
#    /etc/init.d/tclhttpd
# RedHat Linux:
#    /etc/rc.d/init.d/tclhttpd
# HPUX:
#    /sbin/init.d/tclhttpd
#
# The script also needs links from peer directories named
# rc2.d to start the server
# (e.g., make rc2.d/S80tclhttpd a link to ../init.d/tclhttpd)
# and in rc0.d to stop the server, create a link named rc0.d/K20tclhttpd
#

#
PATH=/usr/bin:/bin
TDIR=/ajuba/tclpro1.4/bin
SCRIPT=httpd.tcl
PROG=$TDIR/$SCRIPT

case $1 in
'start')
    if [ -f $PROG ]; then
        $PROG &
    fi   
    ;;
'stop')
    pid=`/usr/ucb/ps -axc | /usr/bin/grep $SCRIPT | /usr/bin/sed -e 
's/^  *//' -e 's/ .*//'`
    if test "$pid"
    then
        echo "Stopping $PROG"
        kill $pid
    fi
    ;;
'restart')
    $0 stop
    $0 start
    ;;
*)
    echo "usage: $0 {start|stop}"
    ;;
esac


regards,

nikos

Re: [Tclhttpd-users] Linux Startup with port 80

[Wart <wa...@ko...>]

Paul Nash wrote:
> What is the best way to have tclhttpd automatically startup under Linux (Suse 9.3). The server is currently in a user home directory -uid 1000 -gid 100.

The tclhttpd source tarball comes with some startup scripts that can be
placed in /etc/init.d (as root) to control startup at boot time:
debian/init.d - startup script for debian
bin/tclhttpd.etc.init - startup script for RedHat

The RPM from Fedora contains another /etc/init.d script suitable for
Fedora-based systems.  These are all good starting points for writing
your own init.d script for Suse.  If you do write one, please let us
know so that we can include it in future tclhttpd releases.

An alternative to using an init.d startup script (which requires root
privileges) is to create a cron job for the user that starts tclhttpd
after a reboot:

@reboot /path/to/tclhttpd start -daemon 1 -config /path/to/your/config

Note, however, that if you want to run tclhttpd on port 80 then it must
be started initially as root so that it can bind to this privileged
port.  Use the 'Config uid ...' configuration in tclhttpd.rc to have
tclhttpd switch to a different user after binding to port 80.

Hope this helps,

--Mike