Results 1 to 3 of 3

Thread: CallMethod for ServerSided SessionManager

  1. #1
    Ext User
    Join Date
    Jul 2010
    Posts
    21

    Default CallMethod for ServerSided SessionManager

    Hi *

    impressed by this post: http://www.davidpirek.com/blog/extst...ssion-provider i wanted to create a server sided session manager, too.
    as you can see david sets the methods of the calls to "GET" and "POST" but when i watch them in firebug, they still seem to be "OPTIONS"-Calls.
    The problem is, that my server-sided-script can only handle get- and post-calls. Thats why i ask myself, why the "method" seems to be overridden and how i can avoid that...

    any idea for this problem?

    thanks a lot, tk

  2. #2
    Ext User
    Join Date
    Jul 2010
    Posts
    21

    Default

    Some additional Information:

    ...this Code...
    Code:
    var sSession = "Hallo";
    var sessionUrl = "http://10.8.102.56:8000/ibis/servlet/IBISHTTPUploadServlet/SessProvTest";
    
    Ext.Ajax.request({
        method : "POST",
        params : {
            clientState : sSession,
            action: 'set'
        },
        url : sessionUrl,
        success: function() {
            alert('Action complete');
        }
    });
    ...results in the following Header...
    Code:
    OPTIONS /ibis/servlet/IBISHTTPUploadServlet/SessProvTest HTTP/1.1
    Host: 10.8.102.56:8000
    User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 (.NET CLR 3.5.30729)
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
    Accept-Language: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
    Accept-Encoding: gzip,deflate
    Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
    Keep-Alive: 115
    Connection: keep-alive
    Origin: null
    Access-Control-Request-Method: POST
    Access-Control-Request-Headers: x-requested-with
    ...i can't find any reason why... any idea anyone?

  3. #3
    Ext User
    Join Date
    Jul 2010
    Posts
    21

    Default

    Hi again...
    I have some News to that... the Host of the Post/Get-receiving Server differs from the Portal-Hostname where the JS is located.
    So the URL for the AJAX-Call contains a "http://<hostname>:<port>/<morestuff>"
    If i change that URL to only "/<morestuff>" it does a real "get" or "post" and no "options"

    But i HAVE to use another server than the portal in this case... hope this information helps you to help me a bit...

    thanks for your work,
    tk

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •