Since the establishment of SP1, we are facing a problem calling the asmx pages with the JMC client code.
The IIS is pointing to the JQ post call on its default 404 page.
We have rollbacked our environment to emphasize this problem due to SP1 and the tests confirm this.
ASP.Net 4.0 - JQuery - IIS 7.5 - Windows 2008 R2 SP1
P>
- Bart Code sample calling (front-end):
// Code to load the word ... $ .ajax ({type: " Post ", URL:" / Handler / Product RTG. AMMX / RAP Product ", Data:" {'IILID': '' + Unique IID + '', Product Id: '' + + Product ID + '', ' Points: "+ points.stosting () +", 'showcasing': "+ showOwnScore.toString () +"} ", Content type:" Application / Jason; Charset = UTF-8 ", Datatype:" Jason ", success: work (reaction) {warning ('success');}, failure: function (warning) Code back-end:
[ScriptService] Public class ProductRating: System.Web.Services.WebService {[WebMethod (EnableSession = true)] Public Rate Product Text Rate Product (Guide Unique ID, Gide Product ID, Int Point, Ball Show Owenscore) {// Implementation} Snapshot 1: with SP1 :
Snapshot 2: Without SP1:
I was able to get this work done on my web with the following additional. Config
I saw another site that suggested to clean the operators, but everything went bad with this update, I was able to call my web services again.
& lt; System.webServer & gt; & Lt; Operators & gt; & Lt; Add name = "asmxRoutingHandler" verb = "*" path = "*. Asmx" type = "System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, version = 3.5.0.0, culture = neutral, publicKeyToken = 31BF3856AD364E35 "/> & Lt; / Operators & gt; & Lt; /system.webServer>
Comments
Post a Comment