This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
About IamJoeG
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About IamJoeG
07-01-2021
2Posts
0Likes
0Solutions
Jul 01, 2021Last Visited
User
Activity
User
Profile
Latest posts by IamJoeG
| Subject | Views | Posted |
|---|---|---|
| 2407 | 07-01-2021 04:59 AM | |
| 2552 | 06-11-2021 05:58 AM |
User Badges
Community Statistics
| Member Since | 05-10-2021 01:42 PM |
| Date Last Visited | 07-01-2021 10:18 AM |
| Posts | 2 |
07-01-2021
04:59 AM
Thanks, any idea what the terminating character for the custom URL would be? For instance, how would one limit to only the top level meaning example.com but not grant access to example.com/file1, example.com/cgi-bin, or example.com/*
... View more
06-11-2021
05:58 AM
Has anyone had luck limiting http methods like PUT to limited URLs? For example, limiting a PUT to https://www.foo.com/ but not to https://www.foo.com/folder1 ? I've created a custom vulnerability that allows the http-method (http-req-header length > 0 which http-method=PUT) in a custom vulnerability but I am having trouble limiting it to the host only portion or the URL/URI. Not sure if this should be further defined in the custom vulnerability, URL category, or just as an fqdn address object? I am trying to think that if I have a use case in the future to allow to https://www.foo.com/folder2 but not https://www.foo.com/folder2/uploads would it be the same solution?
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-01-2021
10:18 AM
|
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks