Bot Emulator 3.5.27 not able to connect to bot getting 301 response

[kausthub]

So i followed the ChatConnector example for Node Js.
This is the log i see in bot emulator
[20:34:29] -> POST 301 [conversationUpdate]

Please help in solving this issue
This issue is on Windows 7

[eanders-ms]

Are you certain is was 301? I'm wondering if it could have been 401.
If 301:

• Was your bot running locally or remotely?

If 401:

• Was your bot configured with MSA appId and password, or running without credentials?

[kausthub]

It was 301 and it was running locally. In fact from the emulator logs I got the payload which it tried to POST to the bot. I did the same using Postman and it worked. Is there something which I am missing here ? But when I used console connector to try out a hello world bot it worked. So only the chat connector is causing issues. Please help me to resolve this Thank you

…

On 8 May 2017 22:31, "Eric Anderson" ***@***.***> wrote: Are you certain is was 301? I'm wondering if it could have been 401. If 301: - Was your bot running locally or remotely? If 401: - Was your bot configured with MSA appId and password, or running without credentials? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#180 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJO3_VlycJ5HwOEXCQLcl11zf7hKRanSks5r30qBgaJpZM4NTLea> .

[eanders-ms]

Could you please copy/paste a few lines from your emulator log showing the error?

[kausthub]

This is all I see in red colour POST 301 [conversation update] Nothing else , I don't know why is it redirecting .

…

On 9 May 2017 02:05, "Eric Anderson" ***@***.***> wrote: Could you please copy/paste a few lines from your emulator log showing the error? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#180 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJO3_VwTlpV-BsktGsG83v9_wmhSxLjFks5r33x9gaJpZM4NTLea> .

[eanders-ms]

A new version of the emulator is available that may be able to provide more information about the 301. Direct download link: https://github.com/Microsoft/BotFramework-Emulator/releases

[kausthub]

Nope still the same issue. Any idea on why this might be returning back 301? I am on the latest 3.5.29 On windows 7

…

On 9 May 2017 22:54, "Eric Anderson" ***@***.***> wrote: A new version of the emulator is available that may be able to provide more information about the 301. Direct download link: https://github.com/Microsoft/BotFramework-Emulator/releases — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#180 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJO3_ctfB-xltXzoNgw9Ok0PHBS2e5xEks5r4KFPgaJpZM4NTLea> .

[Stevenic]

The 301 would have to be coming from something external as there's nothing in the Node SDK that does any sort of redirect. Is it possible that you have a firewall or proxy of some sort running locally? Out of curiosity can you see where it's redirecting you too???

[kausthub]

How can I see where it is redirecting me to ? I clicked on that log and it shows me the body of the post which the emulator sent as the request but where can I see the response ? Thanks for the quick reply

…

On 10 May 2017 23:40, "Steven Ickman" ***@***.***> wrote: The 301 would have to be coming from something external as there's nothing in the Node SDK that does any sort of redirect. Is it possible that you have a firewall or proxy of some sort running locally? Out of curiosity can you see where it's redirecting you too??? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#180 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJO3_QNQieqqq2_TW13SjkFyHH5i3fRZks5r4f2ZgaJpZM4NTLea> .

[eanders-ms]

If the 301 is clickable in the emulator log, clicking it will show the content of the response in the detail view. If the 301 is not hyperlinked, then you'll need to inspect the network traffic using a network debugging tool like fiddler. If you use fiddler, be sure to set your machine's proxy settings to not bypass proxy for local addresses, otherwise you won't see localhost traffic in the fiddler capture.

[kausthub]

So on clicking the 301 response all I can see is a HTML like this <HTML> \r\n <head> <title> redirection <\title> <\head> <body> Redirect <\body>\r\n But no redirect URL anywhere What do I do now ? Thanks

…

On 11 May 2017 10:23, "Eric Anderson" ***@***.***> wrote: If the 301 is clickable in the emulator log, clicking it will show the content of the response in the detail view. If the 301 is not hyperlinked, then you'll need to inspect the network traffic using a network debugging tool like fiddler <https://www.telerik.com/download/fiddler>. If you use fiddler, be sure to set your machine's proxy settings to *not* bypass proxy for local addresses, otherwise you won't see localhost traffic in the fiddler capture. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#180 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJO3_Qt6PXP6k8fz-q6VKK1_5cRVDlvZks5r4pQ3gaJpZM4NTLea> .

[eanders-ms]

Try using fiddler (as described above) to look at the Location header of the 301 response. This header contains the redirect URL.

[eanders-ms]

Going ahead and closing this now. If you'd like further assistance, reply here and we'll reopen it.