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

Port gets unnecesarily rewritten in Proxy #1577

Closed
3 of 10 tasks
ghost opened this issue Jun 27, 2018 · 5 comments · May be fixed by bizoton19/hdwih-hugo-cms#4
Closed
3 of 10 tasks

Port gets unnecesarily rewritten in Proxy #1577

ghost opened this issue Jun 27, 2018 · 5 comments · May be fixed by bizoton19/hdwih-hugo-cms#4
Labels

Comments

@ghost
Copy link

ghost commented Jun 27, 2018

Issue details

I have a link which needs to link to a specific port (which isnt the port that gets proxied), however browsersync rewrites the URL to the Browsersync port.

Steps to reproduce/test case

Assuming:
You are running stock browsersync
The port you are proxying localhost:80 to localhost:3000
You are trying to link to localhost:6426

Write the anchor in the HTML

<a href="http://localhost:6426">test</a>

Observe how the link in the browser gets rewritten to

<a href="http://localhost:3000">test</a>

Please specify which version of Browsersync, node and npm you're running

  • Browsersync [ 2.24.5 ]
  • Node [ 10.4.1 ]
  • Npm [ 6.1.0 ]

Affected platforms

I can now only confirm Linux (host and client) but considering the nature of this bug, I suspect it will be all OS's.

  • linux
  • windows
  • OS X
  • freebsd
  • solaris
  • other (please specify which)

Browsersync use-case

  • API
  • Gulp
  • Grunt
  • CLI

If CLI, please paste the entire command below

{cli command here}

for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync

(laravel-mix-browsersync-official)

@ghost
Copy link
Author

ghost commented Aug 22, 2018

Are bug reports even taken seriously? We're almost 2 months further and not a single comment has been made.

@shakyShane
Copy link
Contributor

@megaxlr hi!

yes they are, but we've been unavailble recently. This weekend we'll be looking at the backlog, thanks for your patience :)

@ghost
Copy link
Author

ghost commented Aug 22, 2018

Good to hear, I was concerned :P

@shakyShane shakyShane added the bug label Aug 26, 2018
@shakyShane
Copy link
Contributor

@megaxlr confirmed bug, it will be looked at :)

@ghost
Copy link
Author

ghost commented Oct 17, 2018

I forgot to look back at this,
Thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant