Thank you
We have the fix ready and should release it shortly. Likely tomorrow.
I apologize for the inconvenience.
Jan Blaha
@admin
Posts made by admin
-
RE: Using the components after updating from v3.6.1 to v4.3.0 gives of errors
-
RE: Report API - async option not returning appPath url.
Yes, the problem is the most likely misconfiguration of your application gateway. I wasn't clear with the
X-Forwarded-For
. There are several headers every reverse proxy needs to send so the backend app can work properly.
https://requestly.com/blog/what-are-x-forwarded-headers-and-why-it-is-used/The
X-Forwarded-For
should contain the client IP and theX-Forwarded-Host
the original host. The correctX-Forwarded-Host
should primarily help. -
RE: Report API - async option not returning appPath url.
The
appPath
is the app subpath which is used to calculate the URL returned in the async report outputLocation
header.When I have in
appPath
config "/myreports" and post tolocalhost
. TheLocation
header will behttp://localhost:5488/myreports/reports/oU0NKlzyrI3fkXdv/status
Doesn't it work for you like that?
The domain in the link is calculated from the request headers also based on the X-Forward-For headers which are typically added by load balancers/application gateways or application servers.
If you post to theyourdomain.com
but getxxx.azurewebsite.net
back in the link, than it could be something wrong with the headers that reach the jsreport. -
RE: Adding an '@ index' to pdfAddPageItem
This is not how the handlebars work. Handlebars doesn't evaluate the expression in here
subSections="Lease {{0}} - Contracted"
because it is a plain string value passed as an argument to the helper.You can implement a helper that will do the replacement for you and prepare the value of
subSections
.
Like here
https://playground.jsreport.net/w/anon/_wQ~5bVn
However there are other approaches you can take, this is just an inspiration -
RE: Authorization for SaaS
Such tools like postman often share the cookies with your browser. So that is why.
You may try with your real client. -
RE: Authorization for SaaS
You need to send the password in the authorization header of course. This standard is called "Basic access authentication".
You need to add a HTTP header to every request looking like this
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
Where the hash is based on username and password: base64(username:password)
https://en.wikipedia.org/wiki/Basic_access_authentication
https://jsreport.net/learn/authentication -
RE: new 4.3.0 won't render PDF
Our official
jsreport/jsreport:4.3.0-full
image works fine. So we need to find what's different in your image.Here is the
dockerfile
used for the official full image, could you compare it with your image?
https://github.com/jsreport/jsreport/blob/master/packages/jsreport/docker/full/Dockerfile -
RE: Authorization for SaaS
jsreportonline currently supports only basic header-based authorization for API requests.
The studio browser authentication is processed through a session cookie.