World: r3wp

How about the trailing slash issue with embed-mode?

Regular cookie expiry, it's up to the developer to handle that (the 
RSP 'set-cookie func is still pending).

What's the issue ?

well, it might just be the demo.. but if you put a url with a slash, 
you get a different result than without the slash.. sometimes

Oldes: I've published some info about PHP support here: http://softinnov.org/cheyenne/blog.cgi?view=0005

thanks.. I will take a look

http://127.0.0.1/testappand   http://127.0.0.1/testapp/are 
two different pages..

You haven't redefined 'dehex have you?

I'm getting odd results ...

The first page takes you to "Welcome to defautl page" and the second 
to the testapp login screen

Terry: that's the intended behaviour, if you request /testapp, it 
calls the 'testapp function in root object (or 'default func if 'testapp 
is not defined), it you request /testapp/, it calls the 'default 
function in the 'testapp object. But that's the demo "site", you 
can change the behaviour in your own "site" if it doesn't fit your 
needs.

Yeah.. that's what I thought.. in the real world that could be an 
issue

It's one thing when you control the URL via the script, it's another 
is someone is requesting the page.

https://www.compkarori.co.nz/newpatient.rsp


if I enter "123 ABC street" on the street1 and submit, the dehex 
result is "3 ABC Stree"

Yeah, I know, but I'm not sure that this kind of thing have to be 
supported at ow level in mod-embed, or left for the developer to 
handled (and adapt the default behaviour).

3 ABC stree

dehex: no, I'm using the native one.

(I hate to be nagging but... any answers to my how-to-write-a-module-question?)

well, I have this:

probe request/content
	street1: url-encode any [ select request/content 'street1 "" ]
print <br/>	
?? street1
print <br/>

probe dehex street1
print <br/>

and I'm not getting the correct answer back!

Maarten, put your order in the httpd.conf file as well.

Marteen: sorry, I've missed your question. Yes, you got it for the 
starting part.

( or mod rather)

OK, now about the ordering... How does that work?

In the modules body you have to implement callbacks (HTTPd phases) 
if you want your module to react on requests. The order is just the 
position of your module's callback for a give phase, among the list 
of other modules.

(You should create a macro key for this answer  Doc)

I should finish the docs :-)

Yep :-)

Thanks, I'll be looking into this a bit more.

Yeah, It's pretty easy once you get your head around it.

Doc, you should create a basic hello world module.

Marteen: see the %docs/developer-guide.html and look at mod-static 
implementation.

There's also the WORD part in modules, allowing you to add config 
options to the httpd.cfg config file, but currently undocumented.

What kind of module are you writing Maarten?

Marteen: you should turn on verbose mode either using -vv (or -vvv) 
option in command line or setting in %cheyenne.r : services/httpd/verbose: 
2

it will show you what module answers on each phase.

How about the listening ports... can you receive a msg on one port, 
and respond on the other?

Terry: sure, but that's no more HTTP protocol ;-)

ftp ?

We'll call it HTTPextreme

lol

or HTTPBigBrother

can we do ftp in uniserve yet?

Just thinking of relaying to my Flash script embedded into the page.

FTP server, a service that I wanted to add to UniServe since a long 
time...

doable?

Ie: I can read a page from my server, and when some particular IP 
reads as well, it can push a message to my page.

that kind of thing

So I can get messages like "Graham just tried circumventing your 
Captcha" messages popping up dynamically on my page ;)

mod-router - a module that routes request based on a sitemap