route().current() broken when using with non-standard port number.
See original GitHub issueI want to check if the named route websites.index is the currently viewed route in the browser. I can’t work out why none of what I have tried is working though.
Route::get('websites', 'WebsiteController@index')->name('websites.index');
window.location.href
"http://localhost:3004/websites"
route().current("websites.index")
false
route('websites.index').url()
"//localhost:3004/websites"
route().current("websites")
false
route().current()
undefined
Ziggy.namedRoutes {
websites.index: {
domain: null
methods: ["GET", "HEAD"]
uri: "websites"
}
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Istio ingressgateway routing broken with two different ... - GitHub
Describe the bug Using https/SDS to secure two gateways(in diff namespaces) which has same port name, the ingressgateway only route to the ...
Read more >Relative URL to a different port number in a hyperlink?
This script will take urls that look like this: [given current url: 'http://some-domain.com:3000/a/path/file.html'] 1.
Read more >Traffic Management Problems - Istio
UF : Failed to connect to upstream, if you're using Istio authentication, check for a mutual TLS configuration conflict. Route rules don't seem...
Read more >Troubleshoot EIGRP Common Issues - Cisco
This document describes how to troubleshoot the most common Enhanced Interior Gateway Routing Protocol (EIGRP) issues.
Read more >Broken packets: IP fragmentation is flawed - The Cloudflare Blog
The maximum packet size that can be transmitted without fragmentation between two remote hosts is called a Path MTU, and can potentially be ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I think this is due to the port number. Recently ran into that in another build.
Perhaps consider renaming your issue “Broken when using with non-standard port number”. I was about to open an issue like that, but it would basically a duplicate of what you seem to be facing.
This issue is still there in the latest version, any solutions?