Cheers.
I finally am able to log onto the on-line editor, however, if I try to go to help or information I am kicked off with an error - invalid password.
Got to be a nasty bug in there cause I are good people
It is frustrating tho'.
Llywelyn
| QUOTE |
| idempotent operations. |
whats that mean then ?
| QUOTE |
| I finally am able to log onto the on-line editor, however, if I try to go to help or information I am kicked off with an error - invalid password. |
do you have script or cookies off and what browers are you using.
I think his refering to the fact that GET is capped at I think its a 256 character string as its sent in the URL and POST is uncapped (well almost) as its sent in the HTTP header of the packet sent by the browser. Hence you get the url with the stuff after the ? in this app and in others when the form POSTs you don't.
The important stuff bit would be because anyone can read/catch a url from a get and its a lot harder to read/catch a POSTed form.
If I'm doing the granny and egg thing here please feel free to twat me round the head and send me on my way :-)
cheers
Pete
| QUOTE (David Bethel @ Jun 30 2004, 11:47 AM) |
| do you have script or cookies off and what browers are you using. |
I've had the same error. Cookies, scripts, everything, on (IE6 XP SP2 RC2). Nothing changed from when I am able to use it without problems, except perhaps the time of day? The time I had this problem (and couldn't log back on) was during the day. i.e. during the time the turns will have been running and the database getting updated. Just a guess, but may be part of the problem?
| QUOTE |
| I think his refering to the fact that GET is capped at I think its a 256 character string as its sent in the URL and POST is uncapped (well almost) as its sent in the HTTP header of the packet sent by the browser. |
The limit seemed to be about 1000-1500 for the GET which was sufficient.
| QUOTE |
| The important stuff bit would be because anyone can read/catch a url from a get and its a lot harder to read/catch a POSTed form. |
The password is POSTed anyway so thats all that really counted for this, everything else was done as GETs cos they seem to survive better when using the back key..... most things don't have reprecussions for reissuing ....
| QUOTE (David Bethel @ Jul 2 2004, 06:04 PM) |
| ..... most things don't have reprecussions for reissuing .... |
I think that's what "idempotent operations" means :)
Still sounds like what the the V.E.T. would do though ;)
| QUOTE |
I think that's what "idempotent operations" means  |
Yup so it does
Big word for programming common sence..... considering i can not even say it, i doubt i will ever use it again though. In any case the POST can be reset by most browsers, its just another key press away. 1. I log-in
2. Screen comes up showing my ships
3. I go to Information
4. Screen comes up --- Invalid Login......
Worked fine yesterday.
Scripts and cookies are activated
Using IE 6.0 under winXP
????
Llywelyn
| QUOTE (David Bethel @ Jul 2 2004, 06:04 PM) |
| The limit seemed to be about 1000-1500 for the GET which was sufficient. |
Actually i belive it's up the browser and webserver how before cutting off get requests, however from rfc 2616 (http 1.1 specification)
| QUOTE |
| Note: Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations might not properly support these lengths. |
However i belive the bigger issue with using GET over POST is that GET is freely cacheable and so it's not that you might get the request twice, but that you might never get it at all (which is obvously a lot harder to fix server side
)Personally i don't think you have any problems currently as the site won't work on less than modern browsers, which don't have the limit, and the server appears to happily accept long URIs. As for caching you should be okay in theory because of the header requests you pass back (although this could explain while session cookies are failing).
The final issue is security, however as were talking http and not https it's not secure anyway and it's not suffiecntly harder to snoop the post data than the get data, just make sure you clear any url cache from the machine you use if it's in a public location
| QUOTE (ptb @ Oct 4 2004, 03:32 PM) |
| i don't appear to have any positions in my drop down list today, whereas on thursday when i did my last set of turns i did. |
I had the same earlier, but retried it half an hour later and it worked ok then.
Mark
cheers mica
It works both ways.