My problem is that I can download passbook passes directly from my api, but with nginx as a reverse proxy in front of my api, safari can no longer open the pass.
I have a system with a ticket-service, an api and an nginx instance that operates as a reverse proxy.
I can request a ticket as a passbook pass file directly from the api through my ios simulator, but when I do the same with nginx between, ios safari returns: "Safari cannot download this file.".
I have tried to do the two requests through chrome on my laptop to check the headers and noticed that nginx adds two; Connection: keep-alive and Server: nginx.
I then tried to add those two to the api as well, just to check that safari don't complain about them and the headers then seem to be the same in chrome.
Headers
HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Etag
Connection: keep-alive
Content-Disposition: attachment; filename="JABJcCu42k"
Content-Encoding: gzip
Content-Length: 72312
Content-Type: application/vnd.apple.pkpass
Pragma: no-cache
Server: nginx
Vary: Accept-Encoding
Date: Thu, 09 Jul 2015 10:01:31 GMT
Does anyone have experience or have an idea of what the problem might be?
Thanks!
BR Fredrik
Related
I installed ThingsBoard CE on premises. I followed
https://thingsboard.io/docs/user-guide/install/ubuntu/
step by step. Installation base is a fresh Ubuntu 22.04 Server install on a virtual host with no other duties. It's an IPv6-only installation with 127.0.0.1 being the only IPv4 address reachable direcly, other IPv4 targets by NAT64/DNS64. From what I see (e.g. by systemctl), all services (Postgresql, Zookeeper, Kafka, Thingsboard) boot up correctly. I installed Thingsboard with the --loadDemo option in step 6 of the instructions. I can log in using the preinstalled accounts. I've changed the passwords. After having checked that things work connecting to localhost:8080, I've installed Apache-based reverse proxies for IPv6 and IPv4 connectivity. This all works.
Next, I continued with the "Hello world" tutorial in
https://thingsboard.io/docs/getting-started-guides/helloworld/
I fire the mocked telemetry transmission using curl:
root#thingsboard:~# curl -v -X POST -d '{"temperature": "24"}' http://localhost:8080/api/v1/xxx/telemetry --header "Content-Type:application/json"
On HTTP level, this seems to work:
* Trying 127.0.0.1:8080...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> POST /api/v1/xxx/telemetry HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Type:application/json
> Content-Length: 21
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200
< Vary: Origin
< Vary: Access-Control-Request-Method
< Vary: Access-Control-Request-Headers
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< Cache-Control: no-cache, no-store, max-age=0, must-revalidate
< Pragma: no-cache
< Expires: 0
< Content-Length: 0
< Date: Wed, 26 Oct 2022 04:33:32 GMT
<
* Connection #0 to host localhost left intact
I do not see, however, the telemetry data in the "Latest telemetry" tab of "My new device" in the tenant's "Devices" dialog. I tried
Sending the data remotely via the reverse proxy or directly to localhost:8080
Sending via IPv6 or IPv4
Replacing the Kafka queuing with in-memory queuing by disabling the Kafka-config lines in thingsboard.conf.
Nothing changed the behaviour a bit. However, making it syntactically incorrect JSON or using a wrong crendential lead to different error result codes so Thingsboard is actually processing the message.
I cannot see anything in the tenant's "Api usage" dialog either as there are only spinning wheels in subframes.
And that's where I am stuck at the moment. I don't have an idea where to look for the problem as I don't even know where I possibly could look.
Can anyone help me?
Best regards,
Dirk
To confirm that the telemetry has correctly reached the device that you have indicated in the post url (/api/v1/xxx/telemetry), you have to set up debug mode in rule chain nodes: https://thingsboard.io/docs/user-guide/rule-engine-2-0/overview/#debugging
All devices messages by default is going to root rule chain, set up debug mode in "Message Type Switch" node and send the same request again, then check events of that node.
If everything goes fine, the output of "Message Type Switch" must be "Post telemetry"
rule chain
"Save Timeseries" is the node that is responsible for saving telemetries.
As often, the problem was at a completely unexpected location: It turned out that ThingsBoard actually processed the events perfectly but my reverse proxy was misconfigured. This was also the reason for
I cannot see anything in the tenant's "Api usage" dialog either as there are only spinning wheels in subframes.
I use Apache as reverse proxy. It needs the proxy, proxy_html and proxy_wstunnel modules enabled and the following configuration (assuming it runs on the same machine as ThingsBoard):
# close off proxying while allowing reverseproxy
ProxyRequests Off
# pass header information through to the proxied host
ProxyPreserveHost On
# mod_proxy_wstunnel for the data websockets
ProxyPass /api/ws/ ws://localhost:8080/api/ws/
# "normal" http reverse proxy
ProxyPass / http://localhost:8080/
ProxyPassReverse / http://localhost:8080/
Now I see the telemetry, I have the dashboards and I can finally continue following the tutorials.
May I suggest the the on-premises installation instructions at least mention this configuration need? It's a trivial pitfall but it can be really frustrating if you forget it and get no hint that there is a problem.
For a spring boot application I was using the docker image tomcat:jdk11-openjdk-buster from 24-Aug-2021 and the swagger-ui.html would load properly.
Today if I build the Dockerfile again with absolutely no changes to the code or Dockerfile, the swagger-ui.html gives,
The weird thing is if I do a curl -I http://xyzxyz.com/warfile/swagger-ui.html I still get 200
HTTP/1.1 200
Date: Fri, 17 Dec 2021 14:16:19 GMT
Content-Type: text/html
Content-Length: 3381
Connection: keep-alive
Accept-Ranges: bytes
Last-Modified: Sun, 14 Jan 2018 16:12:50 GMT
I'm convinced something in the docker image has changed. My initial thought going through the issue list at https://github.com/docker-library/tomcat/issues/252 was maybe the http request is redirecting to https.
But if that were the case wouldn't curl give http 302 instead of a 200?
Is there a way I can know changes made to tomcat:jdk11-openjdk-buster image since August?
If it helps I use path based routing using AWS application load balancer, ECS service and container instance as environment
I checked the Dockerfile for tomcat:jdk11-openjdk-buster and realised the tomcat version has been upgraded from 9.x.x to 10.x.x which was causing my app to not run.
So had to change the base image to tomcat:9-jdk11-openjdk which will at least fix the Tomcat version to 9.x.x and openjdk to 11.x.x
I'm given access to a Rails application which is hosted on a Linux machine. I need to setup a redirection from www to the root domain and, although it can be done via the application using before_filter or route.rb, it's better to do it via the web server. But I don't know what web server it's working on. It may or may not be nginx - I don't know. This is what I need to find out. How can I do that?
Launch your browser.
Open the developer tools, go to the Network tab
Navigate to the web app.
On the left panel, click on any of the loaded resources.
Select the Headers tab and find the Server header within the Response headers section.
This screenshot was made with Chrome (it's slightly different with Firefox or IE)
You can run the following in command line:
curl -I www.yoururl.com
or
curl -I youripaddress
When I run this for my server I see:
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 27 Dec 2014 02:20:01 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 200 OK
This is a super quick way to find out! :)
Good luck!!
I have used RabbitMQ 2.8.6 on Ubuntu 11.10 with success quite long time
and recently decided to upgrade it up to newest version (3.1.x).
I use the custom monitoring for RabbitMQ by using management plugin possibilities.
Unfortunately, on newest version this monitor didn't work by some unknown reason.
I have even tried to send simple request to check workability
curl -i -u guest:guest http://127.0.0.1:55672/api/overview
and get strange response
HTTP/1.1 301 Moved Permanently
Server: MochiWeb/1.0 (Any of you quaids got a smint?)
Location: http://localhost:15672/api/overview
Date: Sat, 11 May 2013 09:37:04 GMT
Content-Length: 0
instead of (as before)
HTTP/1.1 200 OK
Server: MochiWeb/1.1 WebMachine/1.9.0 (someone had painted it blue)
Date: Sat, 11 May 2013 09:54:49 GMT
Content-Type: application/json
Content-Length: 1659
Cache-Control: no-cache
{"management_version":"2.8.6","statistics_level":"fine",...
I noticed that MochiWeb server version is downgraded. Is it a RabbitMQ BUG or maybe my mistake?
Check the official docs here:
http://www.rabbitmq.com/blog/2012/11/19/breaking-things-with-rabbitmq-3-0/
The Management plugins now listens to 15672 and not 55672
Also, it is clear from the response that the page is permanently moved to http://localhost:15672/api/overview
I have a controller action which returns a json structure.
render :json => hash_data
It works for a small dataset in both production and development modes. However, for a large dataset, this only works in development mode. In production mode, only part of json string is returned. Rails version is 3.0.9. In production mode: it goes from a load balancer to nginx; in development mode: I use webrick.
Production Mode Http Response Header:
Cache-Control max-age=0, private, must-revalidate
Connection close
Etag "a7b077a364f849a57ffe582525c98ea1"
Server nginx/1.0.10 + Phusion Passenger 3.0.11 (mod_rails/mod_rack)
Status 304
X-Powered-By Phusion Passenger (mod_rails/mod_rack) 3.0.11
X-Runtime 8.462971
X-UA-Compatible IE=Edge,chrome=1
Development Mode Http Response Header:
Cache-Control max-age=0, private, must-revalidate
Connection Keep-Alive
Content-Length 144561
Content-Type application/json; charset=utf-8
Date Tue, 20 Mar 2012 08:37:30 GMT
Etag "b6b9cdb7811577280320f7a3f50bd937"
Server WEBrick/1.3.1 (Ruby/1.9.2/2010-08-18)
X-Runtime 12.832829
X-UA-Compatible IE=Edge
Even more strange, Chrome works fine for both production and development mode with large dataset. But all other browsers don't work. Any help will be greatly appreciated.
Try thin. You can proxy requests to a Thin backend and still use nginx.
AFAIK from your post and experience with Facebook ETag, you are receiving "304 Not modified" because:
You are sending "HTTP_IF_NONE_MATCH" header from your request in production server
and your record has not been changed.
Your request only gets 200 response if server-side etag does not match to the etag value in Http-If-None-Match. If matches, you will get "304 Not modified"
I guess the production env. turned on etag, and develop env, did not.
You may take a look at this, http://archives.ryandaigle.com/articles/2008/8/14/what-s-new-in-edge-rails-simpler-conditional-get-support-etags