Verb gone missing?

[Hani Suleiman]

Using the latest cvs, the setHttpVerb function seems to have gone  
missing.

Whats the recommended way now of saying that all requests should be  
GET instead of POST? (yes, I know POST is better, but for very boring  
reasons involving NTLM, I need some pages to use GET for all dwr  
requests)



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Joe Walker-3]

I posted some time ago for reasons why anyone would want to do that. Can you tell me more? POST works through NTLM doesn't it?

The reason I got rid if it (and pollMethod) is that DWR only treats them as a hint anyway. There are many cases where it decides that it's going to ignore your request. For example, script tags must use GET, anything with a input[type=file] must use a POST, etc, etc. By removing the option we admit that we can't do what you might have thought we could.

I'm happy to put something back in, but I would prefer to either demonstrate that you don't need it, or find a way to automatically detect your situation and work around it.
Thanks,

Joe.

On Feb 8, 2008 2:20 PM, Hani Suleiman <hani@...> wrote:

Using the latest cvs, the setHttpVerb function seems to have gone
missing.

Whats the recommended way now of saying that all requests should be
GET instead of POST? (yes, I know POST is better, but for very boring
reasons involving NTLM, I need some pages to use GET for all dwr
requests)



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Hani Suleiman]

On Feb 8, 2008, at 9:42 AM, Joe Walker wrote:

>
> I posted some time ago for reasons why anyone would want to do that.  
> Can you tell me more? POST works through NTLM doesn't it?
>
> The reason I got rid if it (and pollMethod) is that DWR only treats  
> them as a hint anyway. There are many cases where it decides that  
> it's going to ignore your request. For example, script tags must use  
> GET, anything with a input[type=file] must use a POST, etc, etc. By  
> removing the option we admit that we can't do what you might have  
> thought we could.
>
> I'm happy to put something back in, but I would prefer to either  
> demonstrate that you don't need it, or find a way to automatically  
> detect your situation and work around it.

The problem we have is that we allow for NTLM to be turned on/off on  
the fly, and users (well, this only applies to admin users, who can  
'override' NTLM) end up with their requests not working. It's an issue  
with NTLM that IE will in certain situations (such as when you switch  
it on/off) it will simply stop sending any POST body data.

However, since we're now using dwr in some fairly crucial admin pages,  
we need them to keep working even when the user does something stupid  
like that, and having the requests on those pages be GETs works around  
it.

Not very compelling I know, but it does save me many  
headaches...Though having said that, I did find a workaround, which to  
do this after dwr is loaded: dwr.engine.transport.xhr.httpMethod =  
'GET';

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Hani Suleiman]

On Feb 8, 2008, at 9:49 AM, Hani Suleiman wrote:

> The problem we have is that we allow for NTLM to be turned on/off on  
> the fly, and users (well, this only applies to admin users, who can  
> 'override' NTLM) end up with their requests not working. It's an  
> issue with NTLM that IE will in certain situations (such as when you  
> switch it on/off) it will simply stop sending any POST body data.
>
FYI, here's the link that explains the issue: http://support.microsoft.com/?id=251404

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Joe Walker-3]

On Feb 8, 2008 2:49 PM, Hani Suleiman <hani@...> wrote:

On Feb 8, 2008, at 9:42 AM, Joe Walker wrote:

>
> I posted some time ago for reasons why anyone would want to do that.
> Can you tell me more? POST works through NTLM doesn't it?
>
> The reason I got rid if it (and pollMethod) is that DWR only treats
> them as a hint anyway. There are many cases where it decides that
> it's going to ignore your request. For example, script tags must use
> GET, anything with a input[type=file] must use a POST, etc, etc. By
> removing the option we admit that we can't do what you might have
> thought we could.
>
> I'm happy to put something back in, but I would prefer to either
> demonstrate that you don't need it, or find a way to automatically
> detect your situation and work around it.

The problem we have is that we allow for NTLM to be turned on/off on
the fly, and users (well, this only applies to admin users, who can
'override' NTLM) end up with their requests not working. It's an issue
with NTLM that IE will in certain situations (such as when you switch
it on/off) it will simply stop sending any POST body data.

However, since we're now using dwr in some fairly crucial admin pages,
we need them to keep working even when the user does something stupid
like that, and having the requests on those pages be GETs works around
it.

Not very compelling I know, but it does save me many
headaches...Though having said that, I did find a workaround, which to
do this after dwr is loaded: dwr.engine.transport.xhr.httpMethod =
'GET';

So my take is that you're probably a bit of a corner case, and that we should document the workaround, but that this is a case where less is more.
Anyone: Feel free to argue.

Joe.