# Packetbeat - full URL on HTTPS traffic? **URL:** \ **Category:** Beats\ **Tags:** packetbeat\ **Created:** [November 23, 2021, 12:00pm UTC](https://discuss.elastic.co/t/packetbeat-full-url-on-https-traffic/289945 "2021-11-23T12:00:10Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![EdgeSync](https://avatars.discourse-cdn.com/v4/letter/e/90ced4/32.png) [@EdgeSync](https://discuss.elastic.co/u/EdgeSync)\ **Post date:** [November 23, 2021, 12:00pm UTC](https://discuss.elastic.co/t/packetbeat-full-url-on-https-traffic/289945/1 "2021-11-23T12:00:11Z")
Is it possible to get the full URL from HTTPS traffic. I would like to be able to view the full URI that a client is attempting to access. e.g. [https://myserver.com/some\_part/this\_file.exe](https://myserver.com/some_part/this_file.exe) I have packetbeat monitoring port 443, and can see the request being logged by packetbeat. I can see the full urls + uri paths for cleartext protocols like HTTP. So wondering if it's possible for HTTPS. Perhaps this is too low down on the network stack? ---
**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\ **Post date:** [November 23, 2021, 5:20pm UTC](https://discuss.elastic.co/t/packetbeat-full-url-on-https-traffic/289945/2 "2021-11-23T17:20:24Z")
No because the path and query parameters are encrypted unless u can do MITM. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 21, 2021, 7:20pm UTC](https://discuss.elastic.co/t/packetbeat-full-url-on-https-traffic/289945/3 "2021-12-21T19:20:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.