►
From YouTube: API Fuzzing Request/Response data overview
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
And
the
thing
that's
different
about
this
is
ins
is
currently
only
the
headers
are
being
displayed
in
the
box
and
we're
going
to
change
that
to
display
we're
going
to
kind
of
recreate
the
first
request
line,
which
is
that
post
path
in
http
1.0
1.1
and
we're
also
going
to
at
the
bottom
after
the
headers
we're
going
to
append
the
body
field
to
this
okay,
and
so,
basically,
what
you're
doing
is
you're
reconstructing
the
http
message,
as
it
would
look
going
out
over
the
network
to
show
it
in
all
its
beauty.
Okay,.
A
B
Yep,
so
if
you
go
back
to
the
that
api
screenshot,
I
gave
you.
B
A
B
At
the
end
of
that
you're
going
to
append
that
body
field
to
it,
okay,
and
so
let
me
show
you
what
it:
what
you'll
I'll
give
you
an
example
of
what
it
should
look
like
here.
Why
don't
you
let
me
share
my
screen:
okay,.
B
B
A
A
B
Some
fuzzing
responses-
this
is
how
our
junit
outputs
right
now,
just
outputs
is
this
ugly
text
blob,
and
this
is
what
we're
gonna.
This
is
some
of
the
data
we're
gonna
end
up
putting
in
so
when
we
go
to
display.
B
So
here's
an
example
here.
If
we
go
to
display
these
messages,
you
know
like
for
the
response
we're
going
to
reconstruct
what
the
message
looks
like
where
we're
going
to
have.
B
You
know
we're
going
to
construct
this
line
with
the
status
code
and
the
stats
message
we'll
construct
the
headers
listing
from
the
headers
array,
where
it's
the
name,
colon
space
and
the
value
we're
going
to
append
after
a
blank
line
the
body,
so
you
notice
that
there's
a
there's
a
line
feed
between
the
headers
and
the
body
here
for
the
request,
the
same
thing
is
going
to
go
on
we're
going
to
have
method,
space,
url
path
and
we're
not
currently
capturing
the
hp
version.
B
A
Which
this
actual
request,
what
form
field
was
in
the
json
response
we
had
just
so
I
can
match
them
up,
because
I
think
that's
where
I'm
getting
confused.
We
have
request
response,
then
supported
messages.
A
B
A
A
B
Mean
the
format
should
be.
You
know
in
that
listing.
That's
that
screenshot
I
sent
you
the
top
level
request
response
which,
which
pre-existed
are
changes.
That's
what
this
actual
actual
request
and
response
fields
are.
A
A
B
And
then
we
have
this
recorded
request
in
response
and
this
basically,
this
will
show
what
a
correct
calling
of
this
api
looks
like
meaning.
This
is
something
we
that
we
recorded
the
proper
calling
and
a
proper
response,
and
the
use
of
this
is
so
the
user
can
then
look
at
these
and
see
what's
supposed
to
happen
compared
to
what
actually
happened
and
then
make
a
decision
so
in
the
ui
for
the
res,
when
we
show
active
response
next
to
it,
we
have
recorded
response.
B
There's
like
two
responses
being
shown.
The
second
one
the
recorded
one
is,
is
coming
out
of
that
supporting
messages.
It's
this
recorded
response
and
I
believe
our
plan
is
to
do
a
diffing
view
on
that
as
well.
A
Yeah
yeah
for
the
follow-up
version,
but
for
mvc
there's
the
three
field
sent
request
the
unmodified
response
and
an
actual
response.
Okay,
is
that
it?
I,
I
think
I'm
trying
I'll
re-review
this
video
recording
to
make
sure.
I
understand-
and
I
might
have
a
follow-up
question
too,
but
it's
not
clear
because
I
I
think
the
struggle
I
had
was
mapping
through
each
of
these
three
fields
and
I
think,
you've
kind
of
covered
that
can
you
see
my
screen
this
one
yeah
yeah?
It
was
like
mapping
these
three.
A
I
I
get
it
like
how
we're
building
the
response-
and
I
think
you
covered-
which
one
of
each
one
of
these
maps
to
the
right.
B
Sent
request
maps
to
the
top
level
request.
A
B
A
Okay,
that's
that
was
the
tricky
thing:
okay,
okay,
perfect!
That's
all
I
needed
and
I'll
be
able
to
build
the
messages
based
off
of
the
other
fields
that
are
in
there.
So
it's
fine
because
we're
constructing
each
line
each
row
of
that
text
anyway,
because
we're
constructing
the
headers
so
I'll
be
able
to
inject
what
we
need
in
there.
The
diffing
stuff.
A
Is
it's
going
to
be
a
follow-up
issue
that
sam
has
already
given
the
thumbs
up
to
kind
of
this
vote
for
nbc,
and
I
think
that's
pretty
much
it.
What
about.
B
A
A
Okay,
all
right
cool
thanks
that
clears
it
up.
I'm
gonna!
I
should
be
able
to
knock
this
out
today.
It's
very
it
should
be
straightforward
in
terms
of
now
that
I
have
the
data's
available
and
I
need
to
construct
the
strings
to
do
each
line
item
there
and
in
terms
of
timing,
I
don't
know,
what's
the
best
way
to
do
this,
with
with
what
you're
blocked
on
so
my
understanding
with
the
work
you
I
know
you
had
elaborating
the
issue,
but
it
was
that
you
need
the
front.
A
A
Okay
and
when,
when
your
match
request
goes
in,
I
guess
it'll
turn
it
on
and
then,
since
we're
not
using
a
feature
flag,
if
it
makes
the
cutoff
for
the
gitlab.com
and
self-managed.
I
guess
is
that
enough
time
like
when,
ideally
when
does
my
stuff
need
to
be
a
master,
to
give
you
enough
time
for
code
review
and
getting
your
stuff
in.
A
B
B
Change
the
report
name
most
of
the
the
bigger
changes
you
know.
Basically,
all
I
need
to
do
in
the
template
is
change
from
you
know
report
judit
to
report
api
fuzzing
and
the
file
name,
so
that
should
go
through
pretty
quick.
Okay.
A
So
you
may
be
able
to
look
at
it
tonight
and
then
maybe,
if
all
things
go
to
plan,
maybe
monday,
hopefully
tuesday,
at
the
latest-
for
the
ui
to
actually
merge
into
masters,
I
I
might
have
to
write
additional
unit
tests
and
stuff,
but
it's
a
monday,
hopefully
tuesday
at
the
latest,
and
if,
if
that
timeline
seems
reasonable,
I
I
guess
I'm
just
trying
to
plan
for
it
or
if
we
need
to
let
you
know,
the
team
know
like
hey,
we'll
be
able
to
get
it
to
gitlab.com,
but
for
self
manager
may
slip,
but.
B
Yeah-
and
I
think
that's
probably
reasonable,
you
know
if
that
happens,
it
happens.
I'm
not
going
to
be
too
stressed
about
it.
B
Also,
to
add
a
little
more
complexity,
I
don't
know
if
you
saw
our
discussion
on
that
ticket
with
neil,
but
you
know
we
want
to
have
the
dashboard
and
the
mr
widget
done
before.
We
merge
that
together.
A
B
Yeah
and
the
the
logic
for
that
is,
you
know
right
now.
The
amount
of
information
we're
giving
in
the
gene
report
makes
it
actionable.
But
if
we
don't
have
that
additional
information
in
then
it's
gonna
become
unactionable.
So
we
don't
want
the
customer
to
go
from
usefulness
to
unusefulness.
So.
A
Now
that
makes
sense.
So
do
you
know
where
that
left
off
with
neil
that
he's
like
okay,
we're
gonna
hold
off
on
that,
because
then
for
me
for
my
stuff
to
go
in,
I
might
have
to
do
a
front-end
feature
flags.
The
concern
was
that
they
didn't
want
to
add
api
fuzzing
as
a
selectable
drop
down.
If
there's
not
going
to
be
any
way
to
surface
api
closing
data
on
security,
dashboard,
okay,
just
fine,
it's
not
hard
for
me
to
do
it.
I.
B
B
A
A
Yeah,
so
that
so
that
was
is
gonna
is
scheduled
for
next
milestone
because
yeah,
because
there's
somewhere
we're
basically
gonna,
do
what
we
did
for
coverage
fuzzing,
where
we
duplicate
there's
a
lot
of
front
end
code
boilerplate
set
up
that
like
I
already
know
what
I
need
to
do,
and
we
have
a
plan
for
that.
But
the
plan
was
to
do
it
next
milestone
because
it's
not
definitely
not
going
into
this
one.
So
it's
only
it
matters
to
me.
A
B
Here
we
go
all
right
so
I'll
make
sure
that
sam
understands
the
milestones
that
we're
talking
about.
B
But
I
think
you
know
like
in
terms
of
like
my
stuff,
I
I
it's
fine,
I
feel
like
it
for
me,
it's
fine
if
it
holds
off
there's
nothing
super
you
know
like
for
me
the
big
my
big
driver
is
hitting
milestones
for
the
acquisition
and
I
think
that
my
worker
has
already
been
accepted
for
that.
In
fact,
seth
might
have
reached
out
to
you
to
to
ask
about
it.
So.
A
Okay,
yeah,
no,
they
haven't
so.
Okay,
that's
fine!
So
will
you
follow
up
on
the
issue
and
let
them
know
or
is
that
something
I
need.
B
A
Perfect
but
yeah,
that's
fine!
In
the
meantime,
then
I
mean
I'm
gonna
continue
forward,
but
the
so
it
sounds
like
right
now.
The
plan
is
that
because
we
need
this
stuff
in
the
mr
widget,
and
that
includes
the
modals
that
are
also
part
of
the
mr
widget,
which
pulls
in
from
the
same
vulnerability
screen
that
we're
doing
here
so
we're
holding
off
on
that.
A
But
so
what
I'll
do
is
I'll
continue
forward
I'll
put
the
front
end
behind
the
feature
flag,
so
it's
not
showing
up
in
the
drop
down
because
until
your
part
comes
in,
we
kind
of
want
to
do
this
all
together.
Okay,
sure,
all
right,
thanks.