08-28-2018, 10:10 AM
So, I did a quick test, and what happened to me is that the browser sends the actual URL once, then sends multiple /favicon.ico requests. The driver sees these and takes that as the command, because it sees a few of them in a row all the same. When you send the command again, it either sends /favicon.ico and that is what matches, but it has no parameters. Or it sends the correct command, which doesn't match anything because the driver ended up training on /favicon.ico
I trained it with Edge instead of Chrome and that worked and I see the parameters.
Ultimately I should probably ship a little trainer program that doesn't do any of that browser silliness. You never know what kind of magic tricks these things are doing when you think you are just sending a simple GET command.
I trained it with Edge instead of Chrome and that worked and I see the parameters.
Ultimately I should probably ship a little trainer program that doesn't do any of that browser silliness. You never know what kind of magic tricks these things are doing when you think you are just sending a simple GET command.
Dean Roddey
Explorans limites defectum
Explorans limites defectum
