Custom Query (1173 matches)
Results (262 - 264 of 1173)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5546 | wontfix | Server hardly hostable behind nginx proxy_pass and https | ||
| Description |
I am currently hosting my GMG instance behind a nginx proxy using the following line: proxy_pass http://localhost:6543; Since the fastcgi configuration is totally not working (flup errors) this is currently the only way I have to host my GMG. It is behind a secured nginx server with letsencrypt support. However API URLs are returning http://localhost:6543/api/... urls because GMG does not know it is behind a proxy. I managed to make everything work with the following nginx config: location /
{
proxy_pass http://127.0.0.1:6543;
proxy_set_header Host $host;
}
And this modification in app.py in order to enforce https: request.environ['wsgi.url_scheme'] = 'https' However this is hacky. I am not familiar enough with wsgi stuff to propose a patch but hosting via proxy should be way simpler than this hacking. Maybe propose new configuration parameters such as ENFORCE_HTTPS or stuff. |
|||
| #5412 | invalid | Add "Accept-Ranges: bytes" response header and support for videos | ||
| Description |
For streaming large (greater than 1GB) WebM videos, support for the "Accept-Ranges: bytes" header indicates to the browser that partial content requests are supported. This allows the viewer to jump around the video without having to wait for the whole video to load. To see this in action, take a large (greater than 1 GB) WebM file and load it onto Mediagoblin, and then try to watch it from the middle. Use the download link to open the video in its own browser tab, and try to watch it in the middle. Again, it will hang for a long time as the data buffers. If you use browser tools to examine the request, the request will have one HTTP 200 response. Host the same video on nginx and watch it through the browser. You will be able to jump around the content as you like. If you examine the network traffic, there will be an HTTP 200 response for the first request and then HTTP 206 Partial Content responses for each click to navigate. I'm going to try to figure this out myself, but Python isn't my normal playground. A Mediagoblin developer will probably be much faster. |
|||
| #989 | fixed | "Add Media" Button location | ||
| Description |
„Add Media“ Button is hidden First you need to click small arrow icon in the upper right to open a hidden area where you can find this button |
|||
