Re: Auth handler and Registry scripts

[prev] [thread] [next] [Date index for 2005/01/19]

* do you know that many browsers don't support an aribary length of get 
requests? That's why big forms often use POST and

* a major disadvantage of GET is that it is visible in browsers history. 
The next one who works on the computer can see what the last person sent 
to your URL which is most of the time not what you want, although he 
can't change anything beside when the GET holds the user/password (e.g. 
after a change password request).

* file-uploads doesn't work

So be aware of these problems when using GET as your forms method.

Tom

Sean Davis wrote:
> 
> On Jan 19, 2005, at 10:11 AM, Sean Davis wrote:
> 
>> This is a simple not-understanding-the-issues question, I'm sure.  I 
>> have an authen handler (that used Apache::Request, Apache::Cookie, and 
>> Apache::Session) in front of a uri serving a Registry script that runs 
>> using CGI.  The script works fine without the handler in place, but 
>> when I put the handler in place (which also seems to do what I want), 
>> I seem to be losing the ability to do post requests (I get the 
>> content, but the changes made on the previous form page are not 
>> reflected on the update).  Is the issue that I need to change all the 
>> post parameters to args for a get and do a redirect?
>>
> 
> I tried it (changing post to get, that is).  Fixed the problem.
> 
> Sorry to waste the list's time.
> 
> Sean
> 
>