[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.aspnet.webservices

Framework version 4322 and HTTP-Get on XML Web Services

Timothy A. Vanover

1/14/2003 7:56:00 PM

I have an issue that I have traced down to an undocumented
change in the 1.1 Framework that is currently being
released with Visual Studio.Net 2003 Final Beta, as well
as .Net Server 2003 RC2. In both instances version
v1.1.4322 of the framework is installed in the
C:\WINDOWS\Microsoft.NET\Framework\ directory along with
any other versions of the framework.

The issue is that on existing Web Services there is no
longer the ability to do an HTTP-GET for web methods. I
have been unable to figure out how to get around this, or
if it is a security setting change of some type that
prohibits this functionality.

I have the same issue on XP with sp1 and Visual
Studio .Net 2003 Final Beta and .Net Server 2003 RC2 \
Visual Studio .Net 2002.

The same web project on another machine running XP \
Visual Studio .Net 2002 (v1.0.3705) has the HTTP-GET
definition and works correctly as did .Net Server 2003 RC
1.

I have searched various articles on Google and the MSDN
library with no sucess.

Can anyone help me figure out what the issue is?

Sincerely,
Timothy A. Vanover MCSD, MCDBA
2 Answers

Yasser Shohoud [MS]

1/14/2003 10:32:00 PM

0

Timothy,

Have you checked out the <protocols> section of machine.config/web.config.
If the line:

<add name="HttpGet"> is not present, the HTTP-GET protocol will not be
supported. Also the line
<remove name="HttpGet"> must not appear anywhere. A sample WebServices
section that enables all the protocols would look something like:

<system.web>
<webServices>

<protocols>

<add name="HttpSoap" />

<add name="HttpPost" />

<add name="HttpGet" />

<add name="Documentation" />

</protocols>

</webServices>

</system.web>

I believe that the HttpGet protocol may have been removed by default but
you should be able to add it back in.

Hope this helps,

Martin

--
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Timothy A. Vanover" <TVanover@Parking.Com> wrote in message
news:583d01c2bbfe$a61645c0$8ef82ecf@TK2MSFTNGXA04...
> I have an issue that I have traced down to an undocumented
> change in the 1.1 Framework that is currently being
> released with Visual Studio.Net 2003 Final Beta, as well
> as .Net Server 2003 RC2. In both instances version
> v1.1.4322 of the framework is installed in the
> C:\WINDOWS\Microsoft.NET\Framework\ directory along with
> any other versions of the framework.
>
> The issue is that on existing Web Services there is no
> longer the ability to do an HTTP-GET for web methods. I
> have been unable to figure out how to get around this, or
> if it is a security setting change of some type that
> prohibits this functionality.
>
> I have the same issue on XP with sp1 and Visual
> Studio .Net 2003 Final Beta and .Net Server 2003 RC2 \
> Visual Studio .Net 2002.
>
> The same web project on another machine running XP \
> Visual Studio .Net 2002 (v1.0.3705) has the HTTP-GET
> definition and works correctly as did .Net Server 2003 RC
> 1.
>
> I have searched various articles on Google and the MSDN
> library with no sucess.
>
> Can anyone help me figure out what the issue is?
>
> Sincerely,
> Timothy A. Vanover MCSD, MCDBA
>

Timothy A. Vanover

1/15/2003 2:17:00 PM

0

This solved the issue.

Thanks,
Timothy A. Vanover MCSD, MCDBA

>-----Original Message-----
>Timothy,
>
>Have you checked out the <protocols> section of
machine.config/web.config.
>If the line:
>
><add name="HttpGet"> is not present, the HTTP-GET
protocol will not be
>supported. Also the line
><remove name="HttpGet"> must not appear anywhere. A
sample WebServices
>section that enables all the protocols would look
something like:
>
><system.web>
> <webServices>
>
> <protocols>
>
> <add name="HttpSoap" />
>
> <add name="HttpPost" />
>
> <add name="HttpGet" />
>
> <add name="Documentation" />
>
> </protocols>
>
> </webServices>
>
></system.web>
>
>I believe that the HttpGet protocol may have been
removed by default but
>you should be able to add it back in.
>
>Hope this helps,
>
>Martin
>
>--
>Please do not send email directly to this alias. This
alias is for newsgroup
>purposes only.
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"Timothy A. Vanover" <TVanover@Parking.Com> wrote in
message
>news:583d01c2bbfe$a61645c0$8ef82ecf@TK2MSFTNGXA04...
>> I have an issue that I have traced down to an
undocumented
>> change in the 1.1 Framework that is currently being
>> released with Visual Studio.Net 2003 Final Beta, as well
>> as .Net Server 2003 RC2. In both instances version
>> v1.1.4322 of the framework is installed in the
>> C:\WINDOWS\Microsoft.NET\Framework\ directory along with
>> any other versions of the framework.
>>
>> The issue is that on existing Web Services there is no
>> longer the ability to do an HTTP-GET for web methods. I
>> have been unable to figure out how to get around this,
or
>> if it is a security setting change of some type that
>> prohibits this functionality.
>>
>> I have the same issue on XP with sp1 and Visual
>> Studio .Net 2003 Final Beta and .Net Server 2003 RC2 \
>> Visual Studio .Net 2002.
>>
>> The same web project on another machine running XP \
>> Visual Studio .Net 2002 (v1.0.3705) has the HTTP-GET
>> definition and works correctly as did .Net Server 2003
RC
>> 1.
>>
>> I have searched various articles on Google and the MSDN
>> library with no sucess.
>>
>> Can anyone help me figure out what the issue is?
>>
>> Sincerely,
>> Timothy A. Vanover MCSD, MCDBA
>>
>
>
>.
>