World: r3wp
[!Cheyenne] Discussions about the Cheyenne Web Server
older newer | first last |
Graham 19-Aug-2009 [5478x5] | well changing the url by putting a timestamp fixes the problem partially. |
HTTP/1.1 200 OK Content-Type: text/html; charset=UTF-8 Date: Wed, 19 Aug 2009 07:41:04 GMT Expires: Wed, 19 Aug 2009 07:41:04 GMT Cache-Control: private, max-age=0 X-Content-Type-Options: nosniff Server: GFE/2.0 Via: 1.1 bc3 Content-Length: 0 Connection: Keep-Alive Set-Cookie: cookies here ... Set-Cookie: user=; Expires=Tue, 18-Aug-2009 07:41:04 GMT; Path=/; HttpOnly Set-Cookie: login=; Expires=Tue, 18-Aug-2009 07:41:04 GMT; Path=/; HttpOnly | |
Reading about etags now ... | |
It's not the document that needs to send back the etag as it never even gets that far. | |
So, perhaps I need to set the etag in the page that lists links? | |
Will 19-Aug-2009 [5483] | why do u have Content-Length: 0 ? this is not valid Set-Cookie: cookies here ... |
Graham 19-Aug-2009 [5484x2] | I scrubbed the cookies from the response |
this is returned by googledocs | |
Will 19-Aug-2009 [5486] | are u reverse proxying ? |
Graham 19-Aug-2009 [5487x2] | no proxies |
made the etag settings ... not helping so going to do a wireshark trace to see if I am setting it | |
Will 19-Aug-2009 [5489] | what if you add response/set-header 'Expires "-1" |
Graham 19-Aug-2009 [5490] | it's caching the whole page ... so it won't see the etags |
Will 19-Aug-2009 [5491x2] | headers you pasted are not coming from cheyenne but from google server, you can't control them |
just to understand, you generate a file and u upload to googledocs, then requests it from google server? | |
Graham 19-Aug-2009 [5493x5] | frustrating .. can't get a trace |
Yes, that's correct. | |
but chrome is not executing the rsp script ... as far as I can see. | |
I think I'll just stick with putting a time stamp on each request to foil the cache | |
Or just stick with FF / IE. | |
Will 19-Aug-2009 [5498x2] | then this has nothing to do with cheyenne, add something like join %? checksum form now/precise ad the end of requested url |
if it is the rsp script that doesnt get executed , please paste headers from rsp response | |
Graham 19-Aug-2009 [5500x2] | ?t= url-encode form now/time/precise |
which rsp response? | |
Will 19-Aug-2009 [5502] | you said "but chrome is not executing the rsp script ... as far as I can see." |
Graham 19-Aug-2009 [5503] | yes, I put a ?? in the script and it doesn't log. |
Will 19-Aug-2009 [5504] | so that is the rsp you request that generate the file and upload it to google |
Graham 19-Aug-2009 [5505] | yes |
Will 19-Aug-2009 [5506] | I'd like to see the response headers of that request , not those from requesting the uploaded file |
Graham 19-Aug-2009 [5507x2] | thi sis the link http://gchiu.no-ip.biz:8000/md/creategoogledoc.rsp?gdoc=simple-letter.rtf&patientid=2832&encounter=none |
but the page does not get executed | |
Will 19-Aug-2009 [5509] | I can't go past http://gchiu.no-ip.biz:8000/md/login.rsp 8) |
Graham 19-Aug-2009 [5510x2] | When I click on that link ... it supposed to execute a script when then sets the response/redirect |
so there is no response from cheyenne .. only from google | |
Will 19-Aug-2009 [5512] | with a redirect and wireshark, u should see both response headers, your browser is requesting two resources, one form Cheyenne, one from the redirected url |
Graham 19-Aug-2009 [5513] | You'd think so .. but the pcap dump is only showing the googledocs response |
Will 19-Aug-2009 [5514x3] | if u private msg me a login/pas I can give it a look |
impossible, that is not how it works, cheyenne responds with a redirect, that is an answer and has a header, the the browser request the redirected url from google server | |
I need to see headers of the redirect response sent from Cheyenne, the problem may be there, if that response hasn't proper Expire, etc.. headers it may get cached by Chrome, and thus the behaviour u see | |
Graham 19-Aug-2009 [5517] | this is the request GET /md/creategoogledoc.rsp?gdoc=simple-letter.rtf&patientid=2832&encounter=none HTTP/1.1 Host: gchiu.no-ip.biz:8000 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://gchiu.no-ip.biz:8000/md/Listgoogledocs.rsp Cookie: RSPSID=QZPTPCZIWWMMYBKWHWRQETGM |
Will 19-Aug-2009 [5518] | I need the response not the request 8) |
Graham 19-Aug-2009 [5519] | Yes .. I know ... that was the end of the "follow tpc stream" |
Will 19-Aug-2009 [5520x3] | umm.. now that sessions are bound to ip I can't hijack your session to check that out ;-) |
got to go, either paste here response headers from cheyenne or private msg me a temp user/login. in the meantime just add a timestamp parameter to the response/redirect url | |
timestamp also for the rsp url | |
Graham 19-Aug-2009 [5523x2] | http://www.compkarori.co.nz:8000 userid/pass Guest/Guest |
You won't be able to create a googledoc though as it requires that your google credentials are stored! | |
Robert 19-Aug-2009 [5525x2] | My reported problem: Doc, I'm not using VALIDATE nor do I check the parameters. Do I have to? I thought Cheyenne does this implicit. |
I expect the problem with the parameter to force the seen side-effects. So before going into deeper analysis I want to fix the parameter problem. Any guide how to handle parameters correctly? | |
Dockimbel 19-Aug-2009 [5527] | Robert, how can Cheyenne know that "quantity" must be an integer! value if you don't tell it? Cheyenne can't validate that implicitly, you have to either use VALIDATE (see API doc) or make your own checking routines. By default, all your GET or POST parameters are treated as string! value. If you need to check for their presence or need to convert them to another datatype, you have to validate the format so that it doesn't error out (or worth, let an hostile request pass). |
older newer | first last |