World: r3wp

.

I have this odd problem with trying to execute a batch script from 
an rsp page.

I do a call/wait and get a return value of 0, but the script doesn't 
actually do what it's supposed to do .. viz. convert a ps file to 
pdf.
but the same batch file called from a rebol console does work.

I don't see why 'call wouldn't work in RSP.

It's very odd...

I put an echo now > when.txt in the .cmd file and it definitely is 
being executed

and returning a 0, even though it doesn't do what it is supposed 
to do ie. invoke ps2pdf

but the same .cmd file works fine in a rebol console.

How about path and other env vars?

paths are all setup correctly

otherwise the cmd file would not work :)

graham, permissions problem?

I wondered about that.  But then it should hang and popup a security 
requester and it doesn't

and since it executes the batch file .. it can't be that.

would it still pop up the sequrity requester if the permissions problem 
is inside the batch file?

how can that happen?

if the batch file calls something of higher privileges. I don't know 
how it works though.

I tried using secure none in the rsp script

made no difference and no requesters came up

I think I have the answer.

I start cheyenne up as a batch file using firedaemon, which turns 
this batch file into a windows service.

If I don't use firedaemon, then the batch file using 'call works. 
 But if I do, it fails :(

So, it appears for the moment I can't use firedaemon to run cheyenne 
as a windows service

anyone got any other ideas on how to run cheyenne as a windows service?

Firedaemon might be running Cheyenne as a different user.

Have you considered reading the source of the .cmd script and translating 
its behavior to REBOL? You might be better able to call the command 
line tools directly rather than through cmd.exe.

It might be faster too.

Had the same result ...

Since my encapped applications work fine under Firedaemon, I am going 
to try and encapCheyenne next.

This was all I was doing:


call/wait "gswin32.exe -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=test.pdf 
-f test.ps"

https://www.compkarori.co.nz/cgi-bin/showfile.rsp?key=#{E7F8390D60C36AFFB11252677A3586A5}

gives an empty value for key

remove the # and it's okay.

bug report :)

it's bug in Rebol's decode-url:

>> probe decode-url https://www.compkarori.co.nz/cgi-bin/showfile.rsp?key=#blabla
make object! [
    user: none
    pass: none
    host: "www.compkarori.co.nz"
    port-id: none
    path: "cgi-bin/"
    target: "showfile.rsp?key="
]

Interesting .. should we Rambo it?

Or, is it because # is not a legal character in a url?

Is there a limit to how much you can send in a Post command?

As you might have read from above, I am attempting to post postscript 
to a RSP script to convert to PDF.
4k of postscript sees the script complete.
But 92Kb of postscript - and I get this response

make object! [
    code: 800
    type: 'user
    id: 'message

    arg1: {Error.  Target url: https://www.compkarori.co.nz:443/cgi-bin/createpdf.rsp 
    could not be retrieved.  Server response: none}
    arg2: none
    arg3: none

    near: [page: read/custom https://www.compkarori.co.nz/cgi-bin/createpdf.rsp
    reduce ['POST join "content=" content]]
    where: none
]

I think a POST should be okay with 100kb of text .. so perhaps there 
is problem with Cheyenne's handling?

Maybe I should try and simulate a multipart form post on the client 
side instead??

Check your httpd.cfg file to see if you find a 'post-max directive.

If you find one, set it to higher limit (unit is Kb) or just remove 
it.

G: # is used to link to anchors.  e.g. http://www.rebol.com/cgi-bin/blog.r?view=0338#comments

you need to encode # with percent encoding, and you need to make 
sure rebol is nod decoding that for you silently (the url! datatype 
does this unfortunately).

# is a legal url char... Rebol's decode-url is full of bugs for example 
this url is bad decoded as well: http://test/path/target?text/something

I did a grep on the sources,and I can only find post-max in 2 files 
...

mod-static
post-max: [integer!] in main

httpd.r
limit: select req/cfg 'post-max

Not in httpd.cfg

I guess I'll just create a limit in httpd.r

Hmm.  Didn't help either.  Still same error.

Checking the server logs .. looks like the post is not even registering 
there either.

does it work if you test it locally without SSL ?