Currently using the highcharts built in exporting (which sends to their server) breaks HTTPS. Our application is served over HTTPS. Is there a way to not break HTTPS without using your own exporting server?
TIA
Unfortunately we don't offer export server via SSL, but your can prepare your own exporting server.
http://www.highcharts.com/component/content/article/2-news/52-serverside-generated-charts
Related
I'm trying to log nuxt-apollo's requests (headers and response), similar to the chrome devtools network tab, but then server-side. How can I do that with the nuxt-apollo module? I'm running nuxt universal mode. I want to do all graphql calls server-side.
did you try this google extension?
https://chrome.google.com/webstore/detail/apollo-client-developer-t/jdkknkkbebbapilgoeccciglkfbmbnfm
for me its the easiest wat to debug graphql request/mutations
I recommended you to check your apollo api in SPA mode after you make sure that is true change to UNIVERSAL!
Because in universal mode you see the result of api in html or js file
I have been trying to access the controller methods (API) of my MVC.NET Core react application hosted on IIS. The application works perfectly except when fetching data from the API.
I am using the template project that visual studio 2019 creates. If I debug locally, the controller can be accessed. I have tried adding rules to the web.config and some working some settings in app.UseMvc(Routes).
Request URL:http://localhost:xx/api/SampleData/WeatherForecasts
Request method:GET
Status code: 404
Version:HTTP/1.1
Referrer Policy:no-referrer-when-downgrade
fetch('api/SampleData/WeatherForecasts')
.then(response => response.json())
.then(data => {
this.setState({ forecasts: data, loading: false });
});
The controller has the route : [Route("api/[controller]")]
It seems that it is trying to find a folder that has the path above and it its not finding it.
HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
Has somebody encountered this? I want to get my app fully working in IIS before I star developing it. Thanks!
When you deploy the app on IIS "usually" it runs on the default port 80 or 443 if https. Maybe your request is hitting the port you are using during development.
When on IIS try to remove the :xx part of your url
I resolved the problem. I did not have .NET Core Run-time Installed on the server machine. https://dotnet.microsoft.com/download
To host the app in IIS it has to be pointing to the publish folder where your {application}.dll exist. From there it will read the config file and start the UI with the back-end.
open terminal (on your project), run: iisexpress-proxy 5000 to 5001
and run your link.
good luck!
my issue is with React, what happens is the url of the api becomes "localhost:80/client/build/api" something....
I´m currently evaluating Web Dav Product for .NET and I´m really impressed. I only noticed that when I´m integrating the sample code (Asp.NetFileSystem) into my existing ASP.NET Web API 2 Project, it doesn´t work with Office Word directly as a save target.
We have Web API 2 with Windows Authentication and CORS Headers on.
Windows Explorer can open and Navigate the WebDAV Folder and I can create new files there. But when I´m saving from word directly, I get errors in Word that the network path does not work / exist. I tried to debug it but it happens
I separated the WebDAV part in it´s own project for test purposes and it works without the problems.
Am I using it wrong in the context of Web API 2, or is this an unsupported usecase?
I´ll try to get fiddler logs to.
Thanks a lot!
Thanks to the IT Hit WebDav we were able to trace the problem down. To work correctly, OPTION requests have to be processed by the WebDAVHandler. We have a custom module which intercepts OPTION requests to handle CORS. Because of our Module, the WebDAVHandler was not able to add the necessary headers, and Office opened the files readonly.
I would like send my url of the web api (different server, different domain...) from my asp net core server to my client angular2.
For the moment I store my settings in typescript config file in my angular2 app.
Thx
For the moment I store my settings in typescript config file in my angular2 app.
This is the way to go.
Alternative
Add another endpoint that you can query to get the config which will contain the endpoint you are looking for (and possibly other stuff).
I need specific guidance about when using a TFS web extension while the TFS instance is exposed over internet using https protocol.
Background: I developed a TFS 2015 web extension using rest api and installed it on our tfs collection using tfs-cli.
After installation and enabling the extension I load this extension; it throws the following error
“Error Code: 500 Internal Server Error. The request is not supported.
(50)”.
During analysis I discovered that the issue is related to our TFS configuration over http and https.
I am experiencing the same error for other 3rd party extensions like FolderManagement and Team Calendar over https. These extensions work great in our TFS 2015 lab environment which is only exposed over http on the domain.
*Let’s take example of the FolderManagement extension available in the marketplace.*
Attempt 1 - previous configuration:
We have an external url say https://tfs.companyname.com/tfs registered in TMG which was routing all traffic to our internal TFS instance say http://machinename:port/tfs
In TFS Admin console notification url was set to https://tfs.companyname.com/tfs
When we accessed extension in TFS web, it didn’t load and in browser debug we got following error:
GET
https://tfs.companyname.com/tfs/_apis/public/gallery/publisher/ms-devlabs/extension/FolderManagement/1.1.10/assetbyname/main.html
“Error Code: 500 Internal Server Error. The request is not supported.
(50)”.
Attempt 2:
Then I changed TFS notification url in Admin console to point to internal instance http://machinename:port/tfs
Now all extensions started working fine when we accessed our TFS using http://machinename:port/tfs.
However when we accessed external url https://tfs.companyname.com/tfs then extensions didn’t work as TMG was forwarding traffic from secure (https) to insecure(http) and caused authorization issues.
Attempt 3 - Current configuration:
On TFS server we added https binding (port 443) to “Team Foundation Server” website and assigned valid certificate. Side note - The certificate is wildcarded *.companyname.com supporting the exposed dns entry for the site.
In the TFS Admin console, the notification url is set to https://tfs.companyname.com/tfs
and server url is also set to https://tfs.companyname.com/tfs
External url https://tfs.companyname.com/tfs is routing traffic to TFS server (machine IP) over 443 port.
Now when we are accessing extension in TFS web, It’s showing same error as mentioned earlier i.e.
GET
https://tfs.companyname.com/tfs/_apis/public/gallery/publisher/ms-devlabs/extension/FolderManagement/1.1.10/assetbyname/main.html
“Error Code: 500 Internal Server Error. The request is not supported.
(50)”.
Given the current configuration I am getting the same behaviour/error for both http and https.
Question: Why does the extension work as expected when all configuration is targeting a TFS installation hosted over http but when exposed over https the web extension behaves differently?
I have to say both http and https can work well with the same configuration for the web extension is impossible. Try below configuration before your deploy your web extension.
Configuring Your Deployment to Require HTTPS with SSL (Optional)
You can require all connections to the TFS application tier to use
HTTPS with SSL. This additional security is optional but recommended.
To require SSL connections
1.On the server that hosts the website that you want to configure, choose Start, choose Administrative Tools, and then choose Internet
Information Services (IIS) Manager.
2.Follow the appropriate steps for your version of IIS:
For deployments that use IIS 7.0:
a.Expand ComputerName, expand Web Sites, and then choose the website
that you want to configure.
b.On the home page for that website, choose SSL Settings.
c.In the SSL Settings pane, select the Require SSL check box.
(Optional) Select the Require 128-bit SSL check box.
d.In Client Certificates, choose Ignore, Accept, or Require, depending
on the security requirements of your deployment.
e.In Actions, choose Apply.
f.Repeat these steps for each website for which you want to require
SSL.
More details about HTTPS with TFS please refer this MSDN link : Set up HTTPS with Secure Sockets Layer (SSL) for Team Foundation Server
This turned out to be TMG related issue. TFS configuration was correct.
Thanks a lot to everyone who helped. This issue can be closed now.
I believe this is a bug in the product. For some strange reason (bad practice) whoever decided to write those image urls didn't honor the current browser url. This would be very simple if they just wrote a relative url.
In my case a have a public https url https://team.devscope.net/tfs/_api..., and an internal https://*:8080/tfs, but the product just invented an unprotected/new url named http://team.devscope.net:8080/tfs/_apis.
result is just an error in the browser: