All custom protocol handlers are called on Windows

[lucasfernog]

I believe the add_web_resource_requested should only be called once and the protocol name needs to be parsed from the URL, calling the proper protocol handler. Currently all handlers are called.

[lucasfernog]

I have a fix for this and I believe this will fix tauri-apps/tauri#2124

[timonwimmer-git]

Maybe I did something wrong - however after trying out your fix, I am still getting that annoying ERR_NAME_NOT_RESOLVED error every third time I open my application.

[wusyong]

@timonwimmer-git Did you try wry with commit after 923d346? Or it's just on tauri?
Tauri hasn't updated to latest update of wry I believe.

If it's on wry, I would really appreciate to see a minimum reproducible example. So I'll could track it more clearly.

[timonwimmer-git]

With commit 923d346!
The thing is, I really can't track it down. If I create a new VM and freshly set-up tauri, it still sometimes happens on the first run! I'll keep digging and get back to you.

[wusyong]

Thanks! Hmm, I'll also test with some examples to see if I can find out at the same time.

[timonwimmer-git]

With commit 923d346, just wry without tauri and using the custom_protocol.rs example (https://github.com/tauri-apps/wry/blob/renovate/windows-0.x/examples/custom_protocol.rs) I consistently got it working!