org.kaazing.specification.ws.extensions.x-kaazing-ping-pong.server.should.reply.to.standard.ping.with.standard.pong.request.rpt Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of specification.x-kaazing-ping-pong Show documentation

Specification for x-kaazing-ping-pong protocol

The newest version!

#
# Copyright 2007-2015, Kaazing Corporation. All rights reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

property key ${ws:handshakeKey()}
property writeMask ${ws:randomBytes(4)}

connect http://localhost:8001/echo
connected

write method "GET"
write version "HTTP/1.1"
write header host
write header "Upgrade" "websocket"
write header "Connection" "Upgrade"
write header "Sec-WebSocket-Key" ${key}
write header "Sec-WebSocket-Version" "13"
write header "Sec-WebSocket-Extensions" "x-kaazing-ping-pong"

read status "101" /.+/
read version "HTTP/1.1"
read header "Upgrade" /(?i:websocket)/
read header "Connection" /(?i:Upgrade)/
read header "Sec-WebSocket-Accept" ${ws:handshakeHash(key)}
read header "Sec-WebSocket-Extensions" /x-kaazing-ping-pong; *(?[a-fA-F0-9]{8})/

# Response to standard PING should be standard PONG
# Note: client must always use a mask when writing to server (see RFC 6455)
write [0x89 0x80] ${writeMask}
read [0x8a 0x00]

# Do clean close
write [0x88 0x80] ${writeMask}
read [0x88 0x00]

# Server is responsible for closing the TCP connection
closed