After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 661530 - The client connects but the server doesn't react on the client's OPTIONS request on windows
The client connects but the server doesn't react on the client's OPTIONS requ...
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-rtsp-server
git master
Other Windows
: Normal critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-10-12 09:56 UTC by josema.alvarez
Modified: 2018-01-13 14:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description josema.alvarez 2011-10-12 09:56:25 UTC 
The problem is in glib. Don't allow multiple watches on the same socket.
https://bugzilla.gnome.org/show_bug.cgi?id=338943

A posible solution is remove all glib watches and implement natively winsockets in rtspserver. 

The changes required are very large and may need a new branch, and also is required some changes in librtsp from plugins-base.
Comment 1 Wim Taymans 2012-12-14 12:10:05 UTC 
Does it work better now after everything is ported to GIO in the git master branch?
Comment 2 josema.alvarez 2012-12-18 16:15:45 UTC 
I have the same problem, no response after send OPTIONS request.

On next post I put debug info
Comment 3 josema.alvarez 2012-12-18 16:17:13 UTC 
0:00:32.069835000  5456     611000 INFO                GST_INIT gst.c:692:init_post: GLib runtime version: 2.32.4
0:00:32.072835000  5456     611000 INFO                GST_INIT gst.c:694:init_post: GLib headers version: 2.32.4
0:00:32.076835000  5456     611000 INFO                GST_INIT gst.c:343:gst_init_check: initialized GStreamer successfully
0:00:32.080835000  5456     611000 DEBUG        rtspmountpoints rtsp-mount-points.c:63:gst_rtsp_mount_points_init:<GstRTSPMountPoints@00669D80> created
0:00:32.085836000  5456     611000 DEBUG             rtspserver rtsp-server.c:777:gst_rtsp_server_create_socket:<GstRTSPServer@006131A0> getting address info of 0.0.
0.0/8554
0:00:32.095836000  5456     611000 DEBUG             rtspserver rtsp-server.c:837:gst_rtsp_server_create_socket:<GstRTSPServer@006131A0> opened sending server socket

0:00:32.101837000  5456     611000 DEBUG             rtspserver rtsp-server.c:865:gst_rtsp_server_create_socket:<GstRTSPServer@006131A0> listening on server socket 0
0673000 with queue of 5
0:00:40.102294000  5456     611000 INFO              rtspclient rtsp-client.c:2341:setup_client: client 00617068 connected to server ip 192.168.0.201, ipv6 = 0
0:00:40.121295000  5456     611000 INFO              rtspclient rtsp-client.c:2344:setup_client: added new client 00617068 ip 192.168.0.201:53725
0:00:40.139296000  5456     611000 DEBUG             rtspserver rtsp-server.c:975:manage_client:<GstRTSPServer@006131A0> manage client 00617068
0:00:40.154297000  5456     611000 DEBUG                default gstrtspconnection.c:3297:gst_rtsp_watch_set_send_backlog: set backlog to bytes 0, messages 100
0:00:40.165298000  5456     611000 INFO              rtspclient rtsp-client.c:2470:gst_rtsp_client_attach: attaching to context 0063E538
Comment 4 Wim Taymans 2013-07-01 15:07:07 UTC 
Does it work now after rewrite to ClientConnection?
Comment 5 Tim-Philipp Müller 2018-01-13 14:24:38 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!