- Are you a spammer?: No
- Registered on: 02/10/2014
- Last connection: 05/24/2017
- Wt (Manager, Developer, 02/10/2014)
Reported issues: 14
- 06:57 pm Wt Help: RE: libwthttp stand-alone server
- Yes, the extra path information will be available in @request.pathInfo()@.
- 01:39 pm Wt Help: RE: access CGI values from WResource::handleRequest
- The latest commit on GitHub contains a patch for @Wt::Http::getCgiValue@.
- 12:23 pm Wt Help: RE: access CGI values from WResource::handleRequest
- Sorry, my mistake. It seems that @REMOTE_USER@ is not present in a header accessible through @headerValue()@.
- 11:44 am Wt Help: RE: access CGI values from WResource::handleRequest
- I believe the REMOTE_USER value should be accessible with @headerValue()@.
It could be useful for development to r...
- 10:53 am Wt Open discussion: RE: Are wt 3.3.7 changes merged to 4.0?
- Sorry, we don't have binary builds of Wt 4 for Windows yet.
You can generate the vcxproj files with CMake.
- 07:04 pm Wt Help: RE: libwthttp stand-alone server
- The resources always respond based on the path. You'll want to filter further inside handleRequest based on @request....
- That's indeed one of the known issues with Wt 3.3.7. It's already been fixed in the master.
- 12:16 pm Wt Help: RE: Web service using WResource
It's not possible at the moment to serve static resources from dedicated processes, as there would be no way t...
- 11:58 am Wt Help: RE: libwthttp stand-alone server
As you can see in the "reference documentation of WServer":https://www.webtoolkit.eu/wt/doc/reference/html/cla...
- 01:49 pm Wt Help: RE: Peformance without threads
- I don't expect the relaying to be very CPU intensive. It does read and process request headers for every HTTP request...
Also available in: Atom