the logs:

```

 ~/soft  ./fiddler-everywhere-0.11.0.AppImage 

[8989:0727/220513.696997:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_fiddle4WxzEm/chrome-sandbox is owned by root and has mode 4755.
[1]    8989 trace trap  ./fiddler-everywhere-0.11.0.AppImage

```

the environment:

Linux pc 5.3.0-3-amd64 #1 SMP deepin 5.3.15-6apricot (2020-04-13) x86_64 GNU/Linux

howdy,

I've downloaded the latest 0.4.0 Fiddler Everywhere. When I run it I get an error - "A JavaScript error occurred in the main process". This occurs every time I launch the app. However it appears to run normally after I dismiss the error dialog.

I'm running Ubuntu 18.0.4:

```

lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

```

 

If you go to Composer and compose a request, if you switch back to inspector for whatever reason (fetch some info for exemple) the composer resets to an empty state!

Platform: Linux.
Product: Progress Telerik Fiddler 0.5.0, downloaded today.

Bug 1: switching between Composer and Inspectors clear Composer fields
Start the program
Click Composer on the right side
Under Headers, fill something in
Click on Inspectors on the right side
Click Composer on the right side
The text under Headers is now resetted

Bug 2: POST body double new line delimiter and body data are formatted as headers
Start the program
Click Composer on the right side
Select POST

Under Headers, fill in a POST header:

Host: example.com
User-Agent: test
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: en-US;q=0.7,en;q=0.3
Content-Type: application/x-www-form-urlencoded
Connection: keep-alive

Under Body, fill in some POST data:

data=1

Click Execute
Click on Inspectors
Click on the result request

Check Headers or Raw, it says:

POST http://example.com HTTP/1.1
Host: example.com
User-Agent: test
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: en-US;q=0.7,en;q=0.3
Content-Type: application/x-www-form-urlencoded
Connection: keep-alive
:
data=1:

Notice the ending, it handles the POST data as parts of the header

Simple: you right click a request, a menu pops-up and you can click "Replay" that request. For extra points: Replay in sequence or parallel

Hey folks. There is a serious lack of guides/tutorials on using fiddler.  

So to set things up you have to use 5 year old stack posts, and if you're lucky things will work.  

 

This has been my biggest issue when it comes to incorporating Fiddler into my workflow. 

 

Right now I'm struggling with setting up a Root CA on Ubuntu (cos the cert is weird).

 

So yeah. Tl:dr Fiddler Everywhere needs guides and tutorials that are easy to follow and available for multiple OS's

To Reproduce:

1. Open Fiddler.

2. Open up a web browser and go to any page that is reasonably large (e.g. https://www.aol.com/)

3. In Fiddler, select the request (click Decode if necessary), then go to the "Raw" tab, scroll down, and click View full response.

Expected result: A decently large window opens with the response

What happens: The window only shows 1 line at a time. See attachment.

Fiddler Everywhere won't even open on my ubuntu 19.04. I can see the logo-loading banner, and then nothing.

Currently when you want to restart the fiddler session you have to quit and re-enter the program as much as I saw.

It would be better to have a "clear" button to erase everything in the current session, so it's easier to manage sessions.

I cannot open Fiddler captures (.saz files) on Fiddler Everywhere on the MacBook.  I realize it's only at v0.2.2, but is there a roadmaap for when Fiddler Everywhere will get such a feature?

I'd like to be able to connect iOS or Android devices to Fiddler and intercept their HTTP / HTTPS traffic. Preferably with as little pain as possible

I would like to be able to copy a selection or everything from a recorded request/response.

 

Sometimes when I close Fiddler Everywhere, the process Fiddler.WebUi stays alive.

When I try opening a second Fiddler Everywhere it can't bind on 8886 and I have to force quit (kill -9) the process before re-opening Fiddler.