信息响应如下所示：

{"entropy":-475136625,"websocket":true}

如果有人想查看请求或响应标头,请告诉我.

更新1：

罗森,谢谢你的回应.关于Spring 4我所知道的一切我都是从你那里学到的:)

Firefox实际上并没有(完全)工作,我无法获得websocket会话,它降级为xhr-streaming.使用xhr-streaming,没有任何问题,但我希望有一个真正的websocket会话.

使用IE浏览器,我不确定删除标题会确认什么？我认为x帧标题只影响了iframe会话,但根本不起作用.当我禁用require cookie时,IE使用xdr-streaming(并且可以工作,虽然无法获取Principal).一旦我启用了cookie,IE就可以正确地使用iframe来尝试ATTEMPTS.但即使标头到位,所有尝试都会失败：

    http://localhost:8084/swtc/rest/hello/info?t=1399328502157

        Key Value
        Response    HTTP/1.1 200 OK
        Server  Apache-Coyote/1.1
        X-Frame-Options SAMEORIGIN
        Access-Control-Allow-Origin http://localhost:8084
        Access-Control-Allow-Credentials    true
        Cache-Control   no-store,no-cache,must-revalidate,max-age=0
        Content-Type    application/json;charset=UTF-8
        Content-Length  78
        Date    Mon,05 May 2014 22:21:42 GMT

LOG: opening Web Socket... 
LOG: opening transport: iframe-htmlfile  url:rest/hello/904/ft3apk1g  RTO:1008 
LOG: Closed transport: iframe-htmlfile SimpleEvent(type=close,wasClean=false) 
LOG: Whoops! Lost connection to undefined 

iframe-htmlfile和iframe-xhr-polling都失败了.我确实清除IE中每次刷新的缓存,我确实在SockJS中启用了调试模式.我会在IE中使用xdr-streaming很好,但我真的需要jsessionid cookie.

有什么想法吗？

另外,如果客户端库代码支持相对路径(它实际上构建了具有相对路径的html文件并且应该工作,但仍然在日志中产生错误),那将是非常好的,即：

SockJsServiceRegistration registration = registry.addEndpoint("/hello").withSockJS().setClientLibraryUrl("js/sockjs-0.3.4.min.js");

这将使部署到生产的痛苦减少.

更新2：

快速摘要：没有变化.

这是我尝试在我的安全配置中使用.headers().和()连接IE9：

LOG: opening Web Socket... 
LOG: opening transport: iframe-htmlfile  url:rest/hello/924/1ztfjm7z  RTO:330 
LOG: Closed transport: iframe-htmlfile SimpleEvent(type=close,wasClean=false) 
LOG: opening transport: iframe-xhr-polling  url:rest/hello/924/cgq8_s5j  RTO:330 
LOG: Closed transport: iframe-xhr-polling SimpleEvent(type=close,wasClean=false) 
LOG: Whoops! Lost connection to undefined 

/ info的请求标头：

Key Value
Request GET /swtc/rest/hello/info?t=1399404419358 HTTP/1.1
Accept  */*
Origin  http://localhost:8084
Accept-Language en-US
UA-cpu  AMD64
Accept-Encoding gzip,deflate
User-Agent  Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Win64; x64; Trident/5.0)
Host    localhost:8084
Connection  Keep-Alive
Cache-Control   no-cache

和响应标头：

Key Value
Response    HTTP/1.1 200 OK
Server  Apache-Coyote/1.1
X-Content-Type-Options  nosniff
X-XSS-Protection    1; mode=block
Cache-Control   no-cache,no-store,max-age=0,must-revalidate
Pragma  no-cache
Expires 0
X-Frame-Options DENY
Access-Control-Allow-Origin http://localhost:8084
Access-Control-Allow-Credentials    true
Cache-Control   no-store,max-age=0
Content-Type    application/json;charset=UTF-8
Content-Length  78
Date    Tue,06 May 2014 19:26:59 GMT

Firefox中没有区别.我尝试打开websocket时遇到同样奇怪的字符串错误,然后回到xhr-streaming：

opening transport: websocket url:rest/hello/849/fy_06t1v RTO:342
SyntaxError: An invalid or illegal string was specified
Closed transport: websocket SimpleEvent(type=close,wasClean=false)
opening transport: xhr-streaming url:rest/hello/849/2r0raiz8 RTO:342
http://localhost:8084/swtc/rest/hello/849/2r0raiz8/xhr_streaming
Web Socket Opened...
>>> CONNECT
accept-version:1.1,10000