Hi
What URI are you specifying while constructing the listener?
relative_uri should contain the URI path, query and fragment path of the request message. Could you also take a look at the request_uri value?
We have tests in our listener testing these scenarios and they are working fine:
Testcase uri_encoding at https://casablanca.codeplex.com/SourceControl/latest#Release/tests/Functional/http/listener/requests_tests.cpp
Testcases at https://casablanca.codeplex.com/SourceControl/latest#Release/tests/Functional/http/listener/request_relative_uri_tests.cpp
relative_uri() returns a web::uri object. This has path(), query() and fragment() APIs that you can call to obtain the URI components.
Thanks
Kavya
What URI are you specifying while constructing the listener?
relative_uri should contain the URI path, query and fragment path of the request message. Could you also take a look at the request_uri value?
We have tests in our listener testing these scenarios and they are working fine:
Testcase uri_encoding at https://casablanca.codeplex.com/SourceControl/latest#Release/tests/Functional/http/listener/requests_tests.cpp
Testcases at https://casablanca.codeplex.com/SourceControl/latest#Release/tests/Functional/http/listener/request_relative_uri_tests.cpp
relative_uri() returns a web::uri object. This has path(), query() and fragment() APIs that you can call to obtain the URI components.
Thanks
Kavya