You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got no mockup designs in mind, but just something to think about:
Chrome and Firefox can be launched from James so that they create a new window that strictly throws requests through James without the user having to adjust any settings.
Other browsers, like IE (and ... Safari? I can't remember) don't have a programmatic way of adjusting the proxy.
We should have some kind of distinction in the browser list for browsers that proxy nicely when clicked
The text was updated successfully, but these errors were encountered:
Maybe we should just show chrome and firefox and add a small text that says something like "we also detected browserX and browserY but you need to configure them manually".
It's kind of confusing if you click on IE and it works but requests don't show up in james.
Absolutely, that makes sense. Ideally, beside each has-to-be-manually-configured browser, we can have a link to our own Wiki docs explaining how to set up proxying for that specific browser/platform, eh?
I've got no mockup designs in mind, but just something to think about:
Chrome and Firefox can be launched from James so that they create a new window that strictly throws requests through James without the user having to adjust any settings.
Other browsers, like IE (and ... Safari? I can't remember) don't have a programmatic way of adjusting the proxy.
We should have some kind of distinction in the browser list for browsers that proxy nicely when clicked
The text was updated successfully, but these errors were encountered: