Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-o on OSX, safari #339

Closed
ainthek opened this issue Jan 23, 2017 · 9 comments
Closed

-o on OSX, safari #339

ainthek opened this issue Jan 23, 2017 · 9 comments

Comments

@ainthek
Copy link

ainthek commented Jan 23, 2017

on OSX, -o opens SAFARI with BAD URI

http://localhost//127.0.0.1:8080

http-server@0.9.0

@ainthek ainthek changed the title on OSX, safari -o on OSX, safari Jan 23, 2017
@derhuerst
Copy link

Related: #264 and #231.

@avinzheng
Copy link

I came across the same problem at 0.10.1.

If posible, I hope "-o chrome" command can be supported to open chrome.

@derhuerst
Copy link

Note that you can manually open the page using open -a Chrome 'http://localhost:8080/'.

@avinzheng
Copy link

@derhuerst Thx for your advice, but I think the correct command is open -a 'Google Chrome' 'http://localhost:8080/' .

@derhuerst
Copy link

derhuerst commented Jul 2, 2017

@imzhengfei Whatever your Chrome .app bundle contains as identifier, yes. It works with any .app macOS is aware of.

@rbiggs
Copy link

rbiggs commented Nov 12, 2017

I was hoping to use http-server as part of a test. However, because of this bug I can't setup a package.json test to work properly:

"scripts": {
    "build": "gulp",
    "test": "http-server ./test -o"
}

I want that to open my test files for me automatically for some mocha tests But on my default browser Safari the url is broken :-(
It works fine if I change my default browser to Firefox or Chrome. However, I do need to run the tests for Safari. Yeah, I could manually open them in Safari. The whole point is that this bug breaks the ability to run automated tests with Safari.

@vitalibozhko
Copy link

Appears to be working fine in 0.11.1

@thornjad
Copy link
Member

@ainthek are you still seeing this problem on the latest version?

@thornjad
Copy link
Member

thornjad commented Feb 5, 2019

Please reopen if this issue shows up again

@thornjad thornjad closed this as completed Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants