Forum Discussion
jmartinez_44554
Nimbostratus
NimbostratusHow to parse a guid from a uri to using in a redirection
I need to keep the guid of a uri and redirect to a new uri using the guid
Whats the best way to accomplish this.
original uri:
en/server/GUID-876D26ED-3B49-41EB-8470-78D3F60F1360addHistory=...
VernonWells
Employee
EmployeeThe URI fragment above is either malformed, or the request URI was structured in an odd. Query parameters start with a question mark (?). The fragment above is, well, a fragment, because after the path, there is a hash (). This is certainly legal, but it means that everything following the hash () are not query parameters. If I substitute a question mark for the hash, this is what I get:
curl -D - 'http://10.11.210.100:8080/en/server/GUID-876D26ED-3B49-41EB-8470-78D3F60F1360?addHistory=true&filename=GUID-BB7DFC3D-E215-4252-AAFA-29EC2AEA5357.xml&docid=GUID-BB7DFC3D-E215-4252-AAFA-29EC2AEA5357&inner_id=&tid=&query=&scope=&resource=&eventType=lcContent.loadDocGUID-BB7DFC3D-E215-4252-AAFA-29EC2AEA5357'
HTTP/1.0 302 Found
Location: http://host.example.com/en/server/GUID-BB7DFC3D-E215-4252-AAFA-29EC2AEA5357
Server: BigIP
Connection: Keep-Alive
Content-Length: 0
Does the client really send the fragment marker () rather than the query marker (?)?
jmartinez_44554This is the actual link: https://livelibrary.osisoft.com/LiveLibrary/content/en/PI%20Server-v2/GUID-876D26ED-3B49-41EB-8470-78D3F60F1360addHistory=true&filename=GUID-BB7DFC3D-E215-4252-AAFA-29EC2AEA5357.xml&docid=GUID-BB7DFC3D-E215-4252-AAFA-29EC2AEA5357&inner_id=&tid=&query=&scope=&resource=&eventType=lcContent.loadDocGUID-BB7DFC3D-E215-4252-AAFA-29EC2AEA5357
