World: r3wp

for verbose either you start cheyenne with -v -vv -vvv .. or look 
at the end of cheyenne.r for these two lines:

uniserve/verbose: any [all [4 < to-integer verbosity 2] 0]
uniserve/services/httpd/verbose: 
any [verbosity 0]

uniserve/verbose: any [all [4 < to-integer verbosity 2] 0]

uniserve/services/httpd/verbose: any [verbosity 0]

sorry altme still has problem with lineendings..

changing verbose in httd.r didn't do anything.

This is Cheyenne/log/default-log ?

Must be logging to screen only

yeah, to console

are you on windows?

dunno but these two lines will bypass verbose set in HTTPd.r or uniserve.r 
so becareful

nope os x

I think there is missing default value for cookie expiration

hmm.. maybe not

Yeah .. windows

Im still not getting any cookies at all  xp FF2 ie7

Can you login to my server?

url?

http://www.compkarori.co.nz

user: dockimbel
pass: 1234

Graham: no problem here

well, I guess you logged in okay

or someone did :)

So, cookies must be working

yeah

what I meant is cheyenne running on localhost  (winxp) is not setting 
any cookies

tis for  me

may be a browser limitation, experienced same issue here depending 
on browsers, also some do not eat cookies when using ip instead of 
hostname in urls

Aren't servers supposed to send cookies with domains ?

Hmm.

Im guessing that using the ip would work.. haven't tried it yet.

Is there a possibility of using the standard sql dialect for 'do-sql 
?


eg [ {insert into table (one, two, three ) values (?,?,?)} a b c 
]

it should work if your DB driver supports it, DO-SQL is just a higher 
level wrapper.

Graham: cookies specification says that if domain attribut in cookie, 
is not provided, "The default value of domain is the host name of 
the server which generated the cookie response."

Graham: it seems that I've found a bug the session expiration in 
Cheyenne, that might be the cause of your error. It's now fixed. 
I'm testing it a little more before releasing it, I'd like to fix 
the cookies issues of Brian and Terry too (one way or another, these 
issues must be related to the info Cheyenne is sending back in the 
response).

Thanks.

qry: [ {select fnames, surname, uid from users where userid = "?" 
and pass = "?" and activ = 'T'} in-user in-pass ]
			sql: do-sql 'remr qry
gives me this

Error Code :  	329
Description : 	script error !

ODBC error: Dynamic SQL Error SQL error code = -206 Column unknown 
? At line 1, column 59.
Near : 	[insert port data 
copy port
]
Where : 	do-sql

but this works;


   qry: rejoin [ "select fnames, surname, uid from users where userid 
   = '" in-user "' and pass = '" in-pass "' and activ = 'T'" ]
			sql: do-sql 'remr qry

oops  ...

ignore

Seems that I found the guilty for the weird session cookie issues, 
need to dig up a little more to confirm the theory.

I'm seeing this after successful inserts 


{make object! [ code: 329 type: 'script id: 'bad-bad arg1: "ODBC" 
arg2: "Invalid cursor state" arg3: none near: [copy port] where: 
'do-sql ]}

where no recordset is being returned

that's coming from the ODBC driver

Yes.

The insert is occuring okay.

but I get this error

so, is cheyenne querying the database after the query expecting a 
response ?

I can bypass the error by wrapping an attempt around the sql insert

do-sql is doing an INSERT on the database port, then a COPY on the 
port. Does your query only require an INSERT on the port and no COPY 
?

let me check RT's doc about that.