Issue 335558 in chromium: Ampersand in path in the Native messaging host manifest

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Bug-Regression OS-Windows

New issue 335558 by jo...@reto.dk: Ampersand in path in the Native
messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/32.0.1700.76 Safari/537.36

Steps to reproduce the problem:
1. Create an extension that connects to a native application through native
messaging.
2. Place the Manifest and the binary file inside of a folder whose name
contains an ampersand (&)

What is the expected behavior?
It should run the binary file when the extension connects to the native
messaging host.

What went wrong?
It gets automatically disconnected from the native messaging host.

Did this work before? Yes Former Chrome version.

Chrome version: 32.0.1700.76 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 12.0 r0

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Labels: Needs-Feedback

Comment #1 on issue 335558 by manoranj...@chromium.org: Ampersand in path

in the Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

josel@, Thanks so much for filing. Can you please provide sample extension
to triage this further?

[chro...@googlecode.com]

Comment #3 on issue 335558 by jo...@reto.dk: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

Just in case it makes any difference to you, I want to add that the same
behavior is expected whether the manifest and the .bat file are located in
the same folder or not.

[chro...@googlecode.com]

Updates:
Cc: rponn...@chromium.org

Comment #4 on issue 335558 by rponn...@chromium.org: Ampersand in path in

the Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

@ jo...@reto.dk: Could you please upgrade to latest stable: 34.0.1847.116
and re-check this issue. If issue is still repro, please update the thread
with latest behavior.

[chro...@googlecode.com]

Updates:
Labels: Cr-Platform-Extensions

Comment #6 on issue 335558 by manoranj...@chromium.org: Ampersand in path

in the Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: ser...@chromium.org
Cc: rdevlin...@chromium.org

Comment #7 on issue 335558 by rdevlin...@chromium.org: Ampersand in

path in the Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

sergeyu@, can you take a look?

[chro...@googlecode.com]

Comment #9 on issue 335558 by donco...@gmail.com: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

I'm also seeing this problem with the '@' sign, which appears to be
blocking a bunch of our 1.6 million IE Tab users who were just upgraded to
native messaging.

[chro...@googlecode.com]

Comment #10 on issue 335558 by donco...@gmail.com: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

I would love to find a workaround, but Sergey, I'm not sure your assessment
is right. I'm looking at the cmd.exe that is used, and it appears to me
that Chrome normally uses quotes. Here's an example:

C:\Windows\system32\cmd.exe
/c "C:\Users\aleksandr.tuzikovrt.ru\AppData\Local\IE
Tab\7.5.3.1\ietabhelper.exe" --parent-window=2360502
chrome-extension://hehijbfgiekmjfkfjpbkbammjbdenadd/ <
\\.\pipe\chrome.nativeMessaging.in.d5a3df7be57bc57f >
\\.\pipe\chrome.nativeMessaging.out.d5a3df7be57bc57f

But if I include an '@' in that path (e.g. aleksand...@rt.ru), it
fails. I'm not sure where or why.

[chro...@googlecode.com]

Comment #11 on issue 335558 by donco...@gmail.com: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

I would love to find a workaround, but Sergey, I'm not sure your assessment
is right. I'm looking at the cmd.exe that is used, and it appears to me
that Chrome normally uses quotes. Here's an example:

C:\Windows\system32\cmd.exe /c "C:\Users\aleksandrt.ru\AppData\Local\IE

Tab\7.5.3.1\ietabhelper.exe" --parent-window=2360502
chrome-extension://hehijbfgiekmjfkfjpbkbammjbdenadd/ <
\\.\pipe\chrome.nativeMessaging.in.d5a3df7be57bc57f >
\\.\pipe\chrome.nativeMessaging.out.d5a3df7be57bc57f

But if I include an '@' in that path (e.g. alek...@rt.ru), it fails. I'm

[chro...@googlecode.com]

Comment #13 on issue 335558 by csa.wood...@gtempaccount.com: Ampersand in

path in the Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

csa.....@sky.com

The problem was with IE Tab Helper not functioning with Chrome
35.0.1916.114m
Many thanks to Don at IE Tab support for sorting this issue out.
IE Tab now works perfectly

[chro...@googlecode.com]

Comment #18 on issue 335558 by m...@chromium.org: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

Ah, thanks. That was indeed the missing link. For the @ case to fail the
path needs to have both a space and an @ in it. One or the other and it
works fine, but if both exists the path needs to be double quoted...

[chro...@googlecode.com]

Comment #22 on issue 335558 by d...@lastpass.com: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

Would calling GetShortPathName() on the path with special characters work
around the problem? I'd imagine that would get rid of the special
characters.

[chro...@googlecode.com]

Comment #23 on issue 335558 by donco...@gmail.com: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

Here are the tickets for the other issues related to using cmd.exe:

Issue #387228, Issue #387233

[chro...@googlecode.com]

Updates:
Owner: ser...@chromium.org
Cc: m...@chromium.org

Comment #24 on issue 335558 by m...@chromium.org: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

Assigning this back to sergeyu@, since I really won't have any time to look
more into this.

[chro...@googlecode.com]

Comment #26 on issue 335558 by donco...@gmail.com: Ampersand in path in the

Native messaging host manifest
http://code.google.com/p/chromium/issues/detail?id=335558

We are still getting daily reports of these path name issues. I hope the
removal of NPAPI support is blocked until this is fixed.

[chro...@googlecode.com]

Comment #27 on issue 335558 by donco...@gmail.com: Ampersand in path in the
Native messaging host manifest
https://code.google.com/p/chromium/issues/detail?id=335558

Would sure love some traction on this bug. I have to send at least one
message like this every single day, and those workarounds don't always
work...

> Hi Tammy,

> Thanks for that info! I understand the problem. There is a bug in
> Chrome that
> prevents the IE Tab Helper from working from directories that have an '&'
> in
> the path.

> You can work around this problem by...

> Let me know how that goes.

> Thanks!
> --
> Don

[chro...@googlecode.com]

Comment #30 on issue 335558 by donco...@gmail.com: Ampersand in path in the
Native messaging host manifest
https://code.google.com/p/chromium/issues/detail?id=335558

Wait, this shouldn't be archived. In what way is this issue "requiring
feedback"?

The issue is perfectly reproducible and there is no further feedback
necessary. I suspect the only reason there hasn't been action on it for a
long time is because no one has been assigned to deal with the bugs in the
extension platform.