We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Has this been tested on windows at all?
When requesting projupdates with the file projupdates_get.json, in the logs I get:
Request GET /projupdates ==> C:/MyWindowsPath//projupdates_get.json
Request GET /projupdates
==> C:/MyWindowsPath//projupdates_get.json
on Windows (fails with 500 Internal Server Error)
500 Internal Server Error
and
Request GET /projupdates ==> /MyLinuxPath//projupdates_get.json
==> /MyLinuxPath//projupdates_get.json
on Linux (does work)
Note the double forward slash appears in both.
The forward/back slashe formatting on Windows also appears to be incorrect by default.
The text was updated successfully, but these errors were encountered:
I found everything working after I disabled
// this.startProxy(); and changed the mock address to the listen address, rather than the listen address + 1.
// this.startProxy();
I'm not totally sure what the difference between: startMock(); and .startProxy(); is.
startMock();
.startProxy();
Apologies for spamming the issues list, but it did work without doing that on Linux - looks like I have majorly hacked things to get it to work.
Sorry, something went wrong.
No branches or pull requests
Has this been tested on windows at all?
When requesting projupdates with the file projupdates_get.json, in the logs I get:
Request GET /projupdates
==> C:/MyWindowsPath//projupdates_get.json
on Windows (fails with
500 Internal Server Error
)and
Request GET /projupdates
==> /MyLinuxPath//projupdates_get.json
on Linux (does work)
Note the double forward slash appears in both.
The forward/back slashe formatting on Windows also appears to be incorrect by default.
The text was updated successfully, but these errors were encountered: