[OASIS Issue Tracker] (AMQPBINDMAP-10) Describe a use-case where redirect might be done

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/AMQPBINDMAP-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59634#comment-59634 ] 

Steve Huston commented on AMQPBINDMAP-10:
-----------------------------------------

John - redir at websocket (pure http level) and again at amqp level.
Rob G: this came from Dave Ingham originally. If we have "dumb" gateway, there needs to be deep inspection of the amqp traffic by the gateway to notice an amqp redirect. This is not going to really happen.

Possibilities:
1. Leave server untouched  - make gateway smarter
2. Turn into some alternate public redirect
3. Let it flow thru unmodified potentially leaking private info

Could possibly use an amqp extension to tell the server the client is on websockets.
This needs to be considered further.

> Describe a use-case where redirect might be done
> ------------------------------------------------
>
>                 Key: AMQPBINDMAP-10
>                 URL: https://issues.oasis-open.org/browse/AMQPBINDMAP-10
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC
>          Issue Type: Task
>          Components: Websockets Binding
>    Affects Versions: csd01
>            Reporter: Steve Huston
>
> At the 5/5/2015 TC meeting there was discussion of how to handle redirects. There was some desire for a use-case to be described where redirect would be needed and how it should work.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)