Can you please explain more precisely what problem you're encountering?
This area is a bit subtle. First, it's worth noting that server-side applications which misbehave when receiving a absolute URL are buggy (according to the standards).
Having said that, traditionally, browsers send a absolute URL when sending HTTP requests through proxies (like Fiddler); they send host-relative URLs for HTTPS requests and when talking directly to origin servers.
Fiddler matches that behavior, and sends the absolute URL only when using HTTP through an upstream proxy, sending host-relative URLs when talking directly to origins or when sending HTTPS requests through a proxy.
Can you please explain more precisely what problem you're encountering?
This area is a bit subtle. First, it's worth noting that server-side applications which misbehave when receiving a absolute URL are buggy (according to the standards).
Having said that, traditionally, browsers send a absolute URL when sending HTTP requests through proxies (like Fiddler); they send host-relative URLs for HTTPS requests and when talking directly to origin servers.
Fiddler matches that behavior, and sends the absolute URL only when using HTTP through an upstream proxy, sending host-relative URLs when talking directly to origins or when sending HTTPS requests through a proxy.
and all request from browsers are like this
request first line should be relative path,not be fullpath,it makes some troubles if server need relative path from head instead of url.