World: r3wp

Could you extract the mod-userdir/get-id function and try to run 
it from a REBOL console using:

    col: #":"
    get-id "www"

Hmm, wait, I think the problem is related to the 'set-gid function.

Are you using the Pro or Command binary? (I guess it is the r139 
one)

I have found a bug with the 'chown function.

Pro 135

Did you see any error in Cheyenne log file (chey-pid-*.log or crash.log)?

Wait, I have r137 now

The errors I quoted are from crash.log. I'll do the -vvvv thing, 
but have to do it later tonight

Ok, I think it is not needed anymore. It seems that the set-gid call 
is failing on your system for group "www". Set-gid returns a logic! 
or none! value if running on a 2.7.8 kernel and an integer! for previous 
kernels (due to different mappings), that is what's causing the error.

If only Carl has freed /Library on Linux instead of adding 'access-os 
native...it would have saved me a lot of coding/debugging time...

Has anyone else than me played with 'access-os native. I can't get 
it return any consistent value...

It seems that the messy behaviour is underneath 'access-os (the setgid/setuid 
OS calls).

i can try on mac too, if u tell me what should be tried

Kaj: I have pushed a fix (needs testing).

Mac: wow, forget about it...

forget => forgot

I am pushing the same fixes for Mac now.

now, im getting multiple errors within the same trace:
	** Access Error : Cannot open /Users/onetom/p/ob/wfm/app-init.r 
	** Access Error : Cannot open /Users/onetom/p/ob/app-init.r 
why is it trying both locations? is it normal?

Never saw such error before.

the html error page says: Redirection Trapped

Means a 30x HTTP code was returned by the request.

needless to say i've created both app-init.r files for the sake of 
the experiment w a content of REBOL[] but im still getting the error

why is it giving me an error page? because of the debug option in 
the config file or because of the -vvvv?

'debug keyword is producing error pages.

ok, it's the debug

the funny thing is im trying to "debug" from the command line and 
i have to login to the app 1st but if the debug flag is on, im getting 
back and error page and multiple session cookies

Multiple?

Cookie	{RSPSID=YVCBKGUZKHKSJGXVCBSTYDIK; RSPSID=YARKPZJMKJUNWDZRFOLUKJTE}
login	"test"
pass	"letmein"
Session ID	"YARKPZJMKJUNWDZRFOLUKJTE"

Remember that you can add debug/off at any time to any page.

ok, i will try that, thx

I guess these 2 sessions ID are coming from 2 different webapps.

Have you tried to define a webapp inside another webapp?

no, i have 1 webapp only now, but let me try in an incognito window

Nested webapps are not supported, the resulting behaviour is undefined.

i was merging multiple webapps under the same vhost, so it mush have 
been some leftover stuff

any example how do u test pages behind a session?

im trying curl -D- -d 'login=test&pass=letmein' -c jar http://localhost:8080/app/login.rsp

but subsequent curl -D- -c jar http://localhost:8080/app/some.html 
still gives me 302 to login.rsp

only session variables are safe?  I must have missed that in the 
docs!

i'd be interested in looking into the sessions during runtime too.. 
can i do it on the cheyenne console by pressing escape?

any example how do u test pages behind a session?

 You shouldn't use AUTH keyword if you don't want the redirection 
 to a login page.

GrahamC: I think it should be explained in the new wiki pages.

Dockimbel: i want the authentication. im just asking how can i test 
it programmatically easily. any idea whats wrong w the curl command 
lines?

i'd be interested in looking into the sessions during runtime too.. 
can i do it on the cheyenne console by pressing escape?
You can access them in 3 different ways:


1) if run from sources, escape in the console, then enter: probe 
uniserve/services/httpd/mod-list/mod-rsp/sessions/queue. Type do-event 
when you want to resume Cheyenne.


2) run the %clients/rconsole.r from the source archive, you will 
have a remote console connected to your local Cheyenne process (try 
on prompt: netstat)


3) add this to the config file in globals section: persist [sessions]. 
When you want to look to the sessions, just stop Cheyenne process, 
a .rsp-sessions file is created holding the session objects.

onetom: sorry, I am not fluent in curl, I need to look for man pages 
for every options...Can't you use REBOL http client for testing?

sure, i can use. i was asking for an example as i how do u do it 
usually

i saw u r using rebol mostly, so i was expecting some rebol example

Does curl handle cookies automatically?

thats whats -c is for

it maintains cookies in a jar

Have you looked into the request/response logs from Cheyenne?

thats what im not sure how to handle w a little code in rebol, that's 
why i was asking u; thought u need have some examples in ur toolbox