Code Monkey home page Code Monkey logo

Comments (5)

Neway6655 avatar Neway6655 commented on August 17, 2024

BTW, I am using version 0.8.1

from moco.

Neway6655 avatar Neway6655 commented on August 17, 2024

I found there was a blog http://dreamhead.blogbus.com/tag/moco/, but that's about 'Content-Length' header not returned situation, while in this case, I found the Content-Length was returned, so it seems a different issue, and I have tested even I upgrade to 0.9.1, this issue still there.
BTW, i am using CXF as the webservice client.

from moco.

dreamhead avatar dreamhead commented on August 17, 2024

Could you please inspect your request/response? I need more information for further action.

from moco.

Neway6655 avatar Neway6655 commented on August 17, 2024

Here is moco server configuration code:
server.post(eq(xpath("//*[local-name()='userId']/text()"), "ema-user-id")).response(
with(pathResource("data/session_login_response.xml")), header("Content-Type", "text/xml"));

Request:
POST /cai3g1.2/services/cai3g1.2/SessionControl?wsdl HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: /
SOAPAction: "CAI3G#Login"
User-Agent: Apache CXF 2.6.0
Cache-Control: no-cache
Pragma: no-cache
Host: localhost:8088
Connection: keep-alive
Content-Length: 267

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><Login xmlns="http://schemas.ericsson.com/cai3g1.2/" xmlns:ns2="http://schemas.ericsson.com/ma/nonSIM/"><userId>ema-user-id</userId><pwd>ema-pwd</pwd></Login></soap:Body></soap:Envelope>

Response:
HTTP/1.1 200 OK
Content-Length: 352
Content-Type: text/xml

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
.xmlns:cai3="http://schemas.ericsson.com/cai3g1.2/">
   <soap:Header/>
   <soap:Body>
      <cai3:LoginResponse>
         <cai3:sessionId>10002</cai3:sessionId>
         <cai3:baseSequenceId>123456</cai3:baseSequenceId>
      </cai3:LoginResponse>
   </soap:Body>
</soap:Envelope>

Please let me know if you need more info.

from moco.

Neway6655 avatar Neway6655 commented on August 17, 2024

Interesting, if I use soapUI or chrome Dev HTTP Client plugin to send the request (even with the same request header and body), moco server response correctly with keep-alive worked. But if I changed to use the code (webservice client generated by cxf) to send the same request, moco server seems close the connection positively. Any idea?

from moco.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.